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
git-sync should use APIs to find upstream #262
Conversation
👋 Welcome back ehelin! A progress list of the required criteria for merging this PR into |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just have one comment!
@edvbld This change can now be integrated. The commit message will be:
Since the source branch of this PR was last updated there has been 1 commit pushed to the
Since there are no conflicts, your changes will automatically be rebased on top of the above commits when integrating. If you prefer to do this manually, please merge
|
/integrate |
Mailing list message from Erik Helin on skara-dev: Changeset: 2f8cfc9 git-sync should use APIs to find upstream Reviewed-by: rwestberg ! bot/src/main/java/org/openjdk/skara/bot/BotRunnerConfiguration.java |
Hi all,
this patch changes
git-sync
to to use theForge
APIs for finding the upstream repository for a personal fork (in case theupstream
remote is missing). The big part of this change is makingForge.repository
returnOptional<HostedRepository>
instead ofHostedRepository
(because a forge may not have the requested repository). Robin, what do you think about these changes?Thanks,
Erik
Testing
git sync
, both with and without anupstream
remoteProgress
Approvers