Skip to content

#2154: Fix IDEasy project creation command in setup documentation#2155

Open
Caylipp wants to merge 3 commits into
devonfw:mainfrom
Caylipp:feature/2154-update-internal-setup-documentation
Open

#2154: Fix IDEasy project creation command in setup documentation#2155
Caylipp wants to merge 3 commits into
devonfw:mainfrom
Caylipp:feature/2154-update-internal-setup-documentation

Conversation

@Caylipp

@Caylipp Caylipp commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

This PR fixes #2154

Implemented changes:

  • Updated the IDEasy project creation command to include the repository URL.

Testing instructions

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

  1. Verify in the setup Documentation the project creation command to include the repository URL.

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"

Updated the IDEasy project creation command to include the repository URL.
@github-project-automation github-project-automation Bot moved this to 🆕 New in IDEasy board Jul 13, 2026
@Caylipp Caylipp self-assigned this Jul 13, 2026
@Caylipp Caylipp added documentation Improvements or additions to documentation internal Nothing to be added to CHANGELOG, only internal story labels Jul 13, 2026
@Caylipp Caylipp moved this from 🆕 New to Team Review in IDEasy board Jul 13, 2026
@oanding-blrng

Copy link
Copy Markdown
Contributor

In the daily meeting of July 15, 2026 it was mentioned, that the proposed change to the documentation would only work for developers with access to the mentioned repo. For extern contributors we should still provide the "old" command.

@coveralls

coveralls commented Jul 15, 2026

Copy link
Copy Markdown
Collaborator

Coverage Report for CI Build 29417551167

Warning

No base build found for commit a88c41e on main.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 72.183%

Details

  • Patch coverage: No coverable lines changed in this PR.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →


Coverage Stats

Coverage Status
Relevant Lines: 16733
Covered Lines: 12587
Line Coverage: 75.22%
Relevant Branches: 7464
Covered Branches: 4879
Branch Coverage: 65.37%
Branches in Coverage %: Yes
Coverage Strength: 3.18 hits per line

💛 - Coveralls

Clarified setup instructions for external contributors and Capgemini developers.
@Caylipp

Caylipp commented Jul 15, 2026

Copy link
Copy Markdown
Contributor Author

In the daily meeting of July 15, 2026 it was mentioned, that the proposed change to the documentation would only work for developers with access to the mentioned repo. For extern contributors we should still provide the "old" command.

Thanks for the comment. I kept the old command for external contributors and added the Capgemini settings repository as an alternative for developers who have access to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation internal Nothing to be added to CHANGELOG, only internal story

Projects

Status: Team Review

Development

Successfully merging this pull request may close these issues.

Update internal setup documentation to use a settings URL instead of default

3 participants