This repository has been archived by the owner on Feb 19, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Builds still failing #5
Comments
@Earu are you alive |
Hi, as of today this action actually does not work the reason is gmod does something extra with the gma file and I haven't been able to reverse engineer that just yet, you should be however capable of using a previous release, it should work just fine so long as you don't have 2fa |
Do you have any idea which release is the last known working?
…________________________________
From: Earu ***@***.***>
Sent: Wednesday, May 25, 2022 4:19:34 AM
To: Earu/GSW-action ***@***.***>
Cc: Fasteroid ***@***.***>; Author ***@***.***>
Subject: Re: [Earu/GSW-action] Builds still failing (Issue #5)
Hi, as of today this action actually does not work the reason is gmod does something extra with the gma file and I haven't been able to reverse engineer that just yet, you should be however capable of using a previous release, it should work just fine so long as you don't have 2fa
—
Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AG73YHREDXUUKPIDU7YTLRLVLXPBNANCNFSM5V5HTCEQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
I can't seem to get this to work—am I doing something wrong?
https://github.com/Fasteroid/prop-hunt-taunts/runs/6433136732?check_suite_focus=true
I tried using modified versions of both the example configuration and the one you're using for EasyChat (which looks newer), but both fail somewhere along the way.
Interestingly, the modified EasyChat variant does actually leave the commit message in the workshop changelog, but it seems to upload some kind of fucked/corrupted gma. In my case the uploaded file is around 8mb, but when you extract it there's "nothing" inside.
So yeah, I need help. Docs were insufficient
The text was updated successfully, but these errors were encountered: