#1651: push and commit status.json files to ide-urls-status after running the URL update worklfow

[AdemZarrouki]

This PR fixes #1651

Implemented changes:

• update the workflow in update-urls.yml to commit and push status.json files to repo ide-urls-status
• status.json should not be pushed to ide-urls
• The migration of status.json is alreday done in #1651: migrate status.json files to ide-urls-status ide-urls-status#1
• Before Merging we need to update ACTION_PUSH_TOKEN so that it have access to the new create repo ide-urls-status. This need to be done by @hohwille as he has access to that functionality.
• After merging this we need to create another PR to delete all status.json files from ide-urls.

---

Testing instructions

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

1. This can be tested in a test branch but for that you need to adapt update-urls.yml to include your test branch. A workflow example was created and it successfully updates both ide-urls and ide-urls-status. https://github.com/AdemZarrouki/IDEasy/actions/runs/26902445623
2. Also you need to include a personal ACTION_PUSH_TOKEN and activate the URL Update workflow in your fork.

---

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"

[coveralls]

Coverage Report for CI Build 26944006085

Coverage decreased (-0.02%) to 71.03%

Details

• Coverage decreased (-0.02%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• 3 coverage regressions across 2 files.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

3 previously-covered lines in 2 files lost coverage.

File	Lines Losing Coverage	Coverage
com/devonfw/tools/ide/version/VersionSegment.java	2	89.24%
com/devonfw/tools/ide/tool/ide/IdeToolCommandlet.java	1	78.33%

---

Coverage Stats

Relevant Lines:	15823
Covered Lines:	11729
Line Coverage:	74.13%
Relevant Branches:	7066
Covered Branches:	4529
Branch Coverage:	64.1%
Branches in Coverage %:	Yes
Coverage Strength:	3.14 hits per line

---

💛 - Coveralls

[tineff96]

I tested the workflow end-to-end in a fork.

---

Test setup:

Created a test branch (test/2003-test-branch) in my fork:

tineff96/IDEasy
tineff96/ide-urls
tineff96/ide-urls-status

Adapted the workflow in tineff96/IDEasy to run against the test branch (test/2003-test-branch)

Executed the workflow based on the provided template
(reference run: https://github.com/AdemZarrouki/IDEasy/actions/runs/26902445623)

---

Result:

The migration of status.json files from ide-urls to ide-urls-status worked as expected.

The workflow correctly commits:

• status.json files are committed to ide-urls-status
• all other files are committed to ide-urls

No unexpected files were committed

Important notes for reviewers / future testers:

Setting up the test environment is slightly non-trivial because it requires:

Forks of both repositories (ide-urls and ide-urls-status)
Adjusting the workflow to use the test branch

You must define the following secrets for commits to work:

ACTION_PUSH_TOKEN
BUILD_USER
BUILD_USER_EMAIL

Without BUILD_USER and BUILD_USER_EMAIL, the commit step will fail.
Conclusion:
From my perspective, the implementation behaves correctly and is ready for review.