#2168: repository remote feature

[QuangAnhLe]

This PR fixes TodoIssueID

Implemented changes:

• Create a new RepositoryRemote record ( similar to RepositotyLink)
• Add git_remote property parsing to RepositoryProperties
• Add remotes field to RepositoryConfig
• Add a addRemote method to ``GitContext interface and implementation
• Call the remote addition in RepositoryCommandlet after cone/pull and before linking
• Add tests for a new feature.
• Changelog entry for the epic : repository remote feature #2168

---

Testing instructions

Please add conscise, understandable instructions on how a reviewer can test/verify the functionality of your contribution here:

1. mvn test -pl cli -Dtest="RepositoryPropertiesTest"

---

Checklist for this PR

Make sure everything is checked before merging this PR. For further info please also see
our DoD.

• When running mvn clean test locally all tests pass and build is successful
• PR title is of the form #«issue-id»: «brief summary» (e.g. #921: fixed setup.bat). If no issue ID exists, title only.
• PR top-level comment summarizes what has been done and contains link to addressed issue(s)
• PR and issue(s) have suitable labels
• Issue is set to In Progress and assigned to you or there is no issue (might happen for very small PRs)
• You followed all coding conventions
• You have added the issue implemented by your PR in CHANGELOG.adoc unless issue is labeled
  with internal
• You have formulated clear instructions on how to test your contribution under "Testing instructions"

Checklist for tool commandlets

Have you added a new «tool» as commandlet? There are the following additional checks:

• The tool can be installed automatically (during setup via settings) or via the commandlet call
• The tool is isolated in its IDEasy project, see Sandbox Principle
• The new tool is added to the table of tools in LICENSE.asciidoc
• The new commandlet is a command-wrapper for «tool»
• Proper help texts for all supported languages are added here
• The new commandlet installs potential dependencies automatically
• The variables «TOOL»_VERSION and «TOOL»_EDITION are honored by your commandlet
• The new commandlet is tested on all platforms it is available for or tested on all platforms that are in scope of the linked issue

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.

❌ Quang Anh Le
❌ QuangAnhLe

---

Quang Anh Le seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coveralls]

Coverage Report for CI Build 29991593234

Coverage increased (+0.02%) to 72.516%

Details

• Coverage increased (+0.02%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• 42 coverage regressions across 5 files.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

42 previously-covered lines in 5 files lost coverage.

File	Lines Losing Coverage	Coverage
com/devonfw/tools/ide/git/repository/RepositoryCommandlet.java	15	72.83%
com/devonfw/tools/ide/git/GitContextImpl.java	12	36.08%
com/devonfw/tools/ide/git/repository/RepositoryProperties.java	9	89.39%
com/devonfw/tools/ide/git/GitContext.java	4	61.54%
com/devonfw/tools/ide/git/repository/RepositoryConfig.java	2	74.19%

---

Coverage Stats

Relevant Lines:	16989
Covered Lines:	12846
Line Coverage:	75.61%
Relevant Branches:	7600
Covered Branches:	4985
Branch Coverage:	65.59%
Branches in Coverage %:	Yes
Coverage Strength:	3.2 hits per line

---

💛 - Coveralls

[QuangAnhLe]

@hohwille If the remotes are automatically created from the git_remote property during repository setup, the onboarding and setup instructions https://github.com/devonfw/IDEasy/blob/main/documentation/contributing/setup.adoc should be updated accordingly, since the manual git remote add upstream step would no longer be required.

[Paras14]

Hi @QuangAnhLe, thanks for your contribution, a few things that stand out:

1. git remote add is not idempotent. The loop you added sits after the createRepository check, so it also runs when the repository already exists, meaning every re-run of ide repository setup calls git remote add upstream... again and git fails with "remote already exists". The same happens within a single run when multiple workspaces are configured, since the additional workspaces are symlinks to the first repository. Please check the existing remotes first and only add the remote if it is missing (or update the URL if it differs).

2. Please rebase onto the current main. GitContextMock was reworked in #1992 improve gitcontextmock #2093 (it now extends GitContextImpl), so your branch currently conflicts in GitContextMock.java. While you are at it, the new mock also lets you record the added remotes so the RepositoryCommandlet part can actually be tested. Right now only the parsing is covered.

3. The new git_remote property needs to be documented in documentation/repository.adoc, both in the table of variables and in the example .properties block above it.

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.

[Paras14]

Suggested change

	void addRemote(Path repository, String name, String url);
	/**
	* Commits the staged changes in the given repository.
	void addRemote(Path repository, String name, String url);
	/**
	* Commits the staged changes in the given repository.

[Paras14]

There should be a blank line after the opening brace('{'). Also the spaces in the comments are a bit off.