You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the code of conduct that this project follows, as appropriate.
I have searched the issue tracker for an issue that matches the one I want to file, without success.
Please describe your issue:
I need to publish my app to a private repo, however when running the publish task it fails with the following output:
$ electron-forge publish
✔ Checking your system
✔ Resolving Forge Config
We need to package your application before we can make it
✔ Preparing to Package Application for arch: x64
✔ Compiling Application
✔ Preparing native dependencies
✔ Packaging Application
Making for the following targets:
✔ Making for target: zip - On platform: darwin - For arch: x64
✔ Making for target: dmg - On platform: darwin - For arch: x64
✔ Resolving publish target: github
Electron forge was terminated:
Please set GITHUB_TOKEN in your environment to access these features
However, I have a GITHUB_TOKEN variable set in my .env file like so:
//.env
export GITHUB_TOKEN=[my github token]
Should I be setting it elsewhere? The documentation does not mention where to put a github token in the event of a private repo so perhaps I am setting it in the wrong place.
Thanks!
The text was updated successfully, but these errors were encountered:
It appears I would have to set the token in the command with the --auth-token flag. Perhaps the error message could be improved a bit, but for now I think this gets me to where I need to go.
Please describe your issue:
I need to publish my app to a private repo, however when running the publish task it fails with the following output:
However, I have a
GITHUB_TOKEN
variable set in my.env
file like so:Should I be setting it elsewhere? The documentation does not mention where to put a github token in the event of a private repo so perhaps I am setting it in the wrong place.
Thanks!
The text was updated successfully, but these errors were encountered: