Skip to content

chore: use Bazel label for config_management patch reference - #324

Merged
pawelrutkaq merged 1 commit into
eclipse-score:mainfrom
fortunaLim:fix/config-management-patch-label
Sep 1, 2026
Merged

pawelrutkaq merged 1 commit into
eclipse-score:mainfrom
fortunaLim:fix/config-management-patch-label

Conversation

@fortunaLim

Copy link
Copy Markdown
Contributor

known_good.json referenced the config_management patch as a relative
path, while all other modules use the Bazel label form:
patches/config_management/001-adapt-proxy-api-....patch
//patches/config_management:001-adapt-proxy-api-....patch

This aligns it with the other seven entries.
bazel_common/score_modules_target_sw.MODULE.bazel is regenerated via
scripts/known_good/update_module_from_known_good.py.

No functional change — the patch resolves to the same file.
Introduced in #299.

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown

The created documentation from the pull request is available at: docu-html

@pawelrutkaq
pawelrutkaq force-pushed the fix/config-management-patch-label branch from cee0973 to 50a2772 Compare September 1, 2026 10:13
@pawelrutkaq
pawelrutkaq merged commit e312aa0 into eclipse-score:main Sep 1, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants