Closed Moosems closed 6 months ago
You will need to create a secret key for it that allows it to create releases and copy the code from the repository with the name TOKEN
@Moosems just pushed a commit to main that should fix the packaging issue you were having.
See a couple small edits below: basically I think we can just use the default GITHUB_TOKEN
for the release job with write permissions, no need for a custom token. Tested this on a private copy of the main repo and it works.
Can you explain why the modular auth examples
works for authenticating with modular? 😄 this is very surprising to me.
Otherwise, with these small changes should be good to merge
@saviorand I don't know why it works. Its how they did it in the Modular/mojo workflows and it just works
so I chose not to question it
I assume it uses some existing token. I could also pass my own token as an env variable
Thanks a lot for the contribution! Merged
Fixes #25