#2168: repository remote feature - #2198
Conversation
Coverage Report for CI Build 32357586330Coverage decreased (-0.07%) to 72.872%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions58 previously-covered lines in 5 files lost coverage.
Coverage Stats💛 - Coveralls |
|
@hohwille If the remotes are automatically created from the |
|
Hi @QuangAnhLe, thanks for your contribution, a few things that stand out:
Also please replace "TodoIssueID" in the PR description with the link to #2168 and adjust the PR title to the form #2168: «brief summary». And the CLA still needs to be signed before this can be merged. |
a5f9cf6 to
6837136
Compare
|
Hi @QuangAnhLe, thanks for the quick turnaround, the fix looks good and GitContextImpl is the right place for it. One thing that stands out: The get-url probe uses the three argument runGitCommand, which defaults to ProcessErrorHandling.LOG_WARNING. On a first setup the remote does not exist yet, so git exits with an error and we log a warning even though everything is fine. That means the noise is moved from the second run to the first one instead of being gone. Please pass ProcessErrorHandling.NONE for the probe using the four argument overload, a failed lookup there is expected and not a problem. |
|
@Paras14 thanks for your review. I have fixed all the issues you pointed out in the ticket. Could you please do one fine review before we merge it into the main branch? |
|
Hello @QuangAnhLe, Looks good to me. |
hohwille
left a comment
There was a problem hiding this comment.
@QuangAnhLe thanks for your PR. This is great work and functionally correct. 👍
I added some code style and design suggestions for further improvements (perfection).
Please have a look and thanks in advance.
Co-authored-by: Jörg Hohwiller <hohwille@users.noreply.github.com>
…tory-remote-feature # Conflicts: # CHANGELOG.adoc
This PR fixes #2168
Implemented changes:
RepositoryRemoterecord ( similar toRepositotyLink)git_remoteproperty parsing toRepositoryPropertiesremotesfield toRepositoryConfigitContextinterface and implementationRepositoryCommandletafter cone/pull and before linkingTesting instructions
Please add conscise, understandable instructions on how a reviewer can test/verify the functionality of your contribution here:
Checklist for this PR
Make sure everything is checked before merging this PR. For further info please also see
our DoD.
mvn clean testlocally all tests pass and build is successful#«issue-id»: «brief summary»(e.g.#921: fixed setup.bat). If no issue ID exists, title only.In Progressand assigned to you or there is no issue (might happen for very small PRs)with
internal