-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hardcoded API url leads to bad credentials error on GitHub Enterprise server #90
Comments
Thanks for filing an issue! I never used this for Enterprise accounts, so I didn't know that this issue exists. I'll see what I can do. |
@Th3S4mur41, I have merged potential fix for this on #91, could you please try to use the master branch version of To use the master branch version, please change the action version in the workflow file to - name: Check PR semantics
uses: Namchee/conventional-pr@master |
With Namchee/conventional-pr@master we don't have the mentioned error anymore |
Thanks for confirming! WIll release a new version soon. UPDATE: I have release |
@all-contributors please add @Th3S4mur41 for bug |
I've put up a pull request to add @Th3S4mur41! 🎉 |
Running the conventional-pr action on an on premise GitHub Enterprise server results in a bad crendentials error.
The error is misleading though and results from the fact that the action is trying to fetch the pull request data from github.com instead of the actual GitHub server.
All references to
https://api.github.com
should be replaced through${{github.api_url}}
to allow the action to work on Enterprise serverThe text was updated successfully, but these errors were encountered: