-
Notifications
You must be signed in to change notification settings - Fork 53
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
GitHub Enterprise private repository action fails #923
Comments
is the address valid? It uses the GitHub server URL from the action-ros-ci/src/action-ros-ci.ts Line 631 in 8bcafc2
Now that I'm looking at the code, though, it's probably because the code that sets up authentication using the provided token uses
It should use the URL from the This does mean you couldn't access private repos on github.com from an enterprise server using a token from github.com saved in the enterprise server, but I don't know if that's a common use-case. |
Thank you @christophebedard! The branch solved the issue. I agree that private repos from github.com while on GitHub Enterprise seems unlikely, though perhaps one day someone will make an issue for this. I imagine this would require a fair amount of restructuring to work. |
Yeah, we'd just need to change the |
Released as |
Description
I am using a mirrored action-ros-ci repository to use on an Enterprise server. The action fails due to an issue seemingly related with Git and the way credentials are handled.
Expected Behavior
What I would expect is that this error would not happen and it would continue on into the build process.
Actual BehaviorWhen attempting to run the following:
The action fails at:
To Reproduce
Have the Git repository on an Enterprise server and run the above GitHub action.
Navigate to details of failed action
Look under
Invoking: bash -c,vcs import --force --recursive src/ < package.repo
System (please complete the following information)
Additional context
There are no .repos dependencies specified for this repository.
This seems to possibly be an intersection of #533, #691, and #835.
I know this is hard to reproduce and I am happy to help. I am not very experienced with TypeScript however.
The text was updated successfully, but these errors were encountered: