how cool would it be for them to use that super technological system called *email* to notify authors about whats happening?
That would be nice. I *still* can't commit to the LibPeriodicTable repo. I understand that this transition is complicated, but I don't think Overwolf realizes how important communication is. I opened a ticket about the commit issue, they said they were looking into it and then the ticket autoclosed. Umm, thanks?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Today when I tried to commit some changes for my addon, I got this error:
Command: Commit
Error: Commit failed (details follow):
Error: Access to '/wow/gtfo/!svn/me' forbidden
I was able to checkout just fine, but commits aren't working now. Branching doesn't work either.
I got an e-mail from support today. I basically needed to generate a new API token at https://authors.curseforge.com/account/api-tokens and use that as my password for my repo. All is good now.
Thanks a lot for this information.
Sincerely
Holger -> Reglohpri
Hello,
I have the same error since yesterday (Access to '/wow/gtfo/!svn/me' forbidden).
I tried to generate a new API token but it did not help.
I tried to do the default TortoiseSVN "Clean up..." and now I have a new error:
Error: Commit failed (details follow):
Error: Can't create directory
Error: '/media/data/repos/wow/deadpool/db/transactions/243-6y.txn': No such file or
Error: directory
Anyone having same issues?
Ok, Curseforge is actually in read-only mode :)
https://twitter.com/CurseForge/status/1333414646552752129
how cool would it be for them to use that super technological system called *email* to notify authors about whats happening?
That would be nice. I *still* can't commit to the LibPeriodicTable repo. I understand that this transition is complicated, but I don't think Overwolf realizes how important communication is. I opened a ticket about the commit issue, they said they were looking into it and then the ticket autoclosed. Umm, thanks?