Skip to content

Feature/2168 repository remote feature#2198

Open
QuangAnhLe wants to merge 9 commits into
devonfw:mainfrom
QuangAnhLe:feature/2168-repository-remote-feature
Open

Feature/2168 repository remote feature#2198
QuangAnhLe wants to merge 9 commits into
devonfw:mainfrom
QuangAnhLe:feature/2168-repository-remote-feature

Conversation

@QuangAnhLe

@QuangAnhLe QuangAnhLe commented Jul 21, 2026

Copy link
Copy Markdown

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

CLAassistant commented Jul 21, 2026

Copy link
Copy Markdown

CLA assistant check
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.

@QuangAnhLe QuangAnhLe self-assigned this Jul 21, 2026
@QuangAnhLe
QuangAnhLe requested a review from hohwille July 21, 2026 15:38
@QuangAnhLe QuangAnhLe moved this from 🆕 New to Team Review in IDEasy board Jul 22, 2026
@QuangAnhLe QuangAnhLe moved this from Team Review to 🏗 In progress in IDEasy board Jul 22, 2026
@quando632 quando632 moved this from 🏗 In progress to Team Review in IDEasy board Jul 22, 2026
@coveralls

coveralls commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

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

Coverage Status
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

Copy link
Copy Markdown
Author

@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.

@QuangAnhLe QuangAnhLe closed this Jul 23, 2026
@github-project-automation github-project-automation Bot moved this from Team Review to ✅ Done in IDEasy board Jul 23, 2026
@QuangAnhLe QuangAnhLe reopened this Jul 23, 2026
@QuangAnhLe QuangAnhLe moved this from ✅ Done to Team Review in IDEasy board Jul 23, 2026
@QuangAnhLe QuangAnhLe moved this from Team Review to 🏗 In progress in IDEasy board Jul 23, 2026
@Paras14 Paras14 moved this from 🏗 In progress to Team Review in IDEasy board Jul 23, 2026
@Paras14 Paras14 self-assigned this Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Team Review

Development

Successfully merging this pull request may close these issues.

5 participants