Closed elliottower closed 1 year ago
Working on fixing the git issue with a private access token but I think it's definitely undesirable behavior to have the yml file permanently change how the package functions afterwards with no obvious way to fix it (tried building without the test server then running that but it didn't work, tried uninstalling pygbag)
Okay I've solved the error with the yml file, it needs write permission. Can be added with a private token, or through github repo settings, or simply by changing
permissions:
contents: read
to
permissions:
contents: write
I get this message whenever I try to run
pygbag [repo_name]
now, after I added the workflow yml file, pushed it to github to test, got a few errors I couldn't figure out, and then removed it.Then when I try to click the link or load localhost:800 myself it just never loads the page.
Seems to be stuck replacing with github.io but it also uses the pygame web repository rather than my own, probably an environment variable issue or something.
Warnings and errors which I got when using the github action:
Errors: