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
cli: make it possible to configure forge name #1076
Conversation
|
Webrevs
|
Looks good in general, but how about also storing this configuration automatically as well when auto-detection completes successfully (if it's not configured yet)? That way everyone could benefit from it on subsequent runs without having to configure it manually. |
Good idea! See the latest commit for an implementation |
@edvbld This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 5 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the
|
/integrate |
@edvbld Since your change was applied there have been 5 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit cd84028. |
Hi all,
please review this patch that makes it possible to configure the forge name for a repository using
git config forge.name
, for examplegit config forge.name github
. This can be useful for speeding up the forge selection logic inForge.from
so that the code doesn't have to query multiple candidate forges.Testing:
Thanks,
Erik
Progress
Reviewers
Download
To checkout this PR locally:
$ git fetch https://git.openjdk.java.net/skara pull/1076/head:pull/1076
$ git checkout pull/1076
To update a local copy of the PR:
$ git checkout pull/1076
$ git pull https://git.openjdk.java.net/skara pull/1076/head