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
When I using Github enterprise server with our custom domain, we can simply fetch repo from github.com, but when pushing to internal repo, the error log shows:
fatal: repository 'https://github.com/<org-name>/<repo-name>/' not found
In fact, the behavior is right because we do not have that repo on github.com, but only in our Github enterprise server.
I create this actions file in our internal repo in our Github enterprise server to sync from github.com.
As we using custom domain rather than github.com, I think it is good to have an option to change the prefix or the full repository name before we set the "destination branch", for example, add a destination_repo option in actions.
The text was updated successfully, but these errors were encountered:
* add a bunch of new inputs into the action to allow a remote repo/host to be used as the upstream or destination of the sync.
* the new API surface on the action isn't the best but should be compatible with the existing usage (relying on running the workflow on the source repo and read in the builtin env vars from GitHub Actions)
related: repo-sync#114
When I using Github enterprise server with our custom domain, we can simply fetch repo from github.com, but when pushing to internal repo, the error log shows:
In fact, the behavior is right because we do not have that repo on github.com, but only in our Github enterprise server.
I create this actions file in our internal repo in our Github enterprise server to sync from github.com.
As we using custom domain rather than github.com, I think it is good to have an option to change the prefix or the full repository name before we set the "destination branch", for example, add a
destination_repo
option in actions.The text was updated successfully, but these errors were encountered: