Skip to content

Add tool requirements list#2636

Open
PandaeDo wants to merge 4 commits intoeclipse-score:mainfrom
qorix-group:vohae_tool_requirements
Open

Add tool requirements list#2636
PandaeDo wants to merge 4 commits intoeclipse-score:mainfrom
qorix-group:vohae_tool_requirements

Conversation

@PandaeDo
Copy link
Contributor

@PandaeDo PandaeDo requested a review from a team as a code owner February 27, 2026 15:10
@github-actions
Copy link

⚠️ Docs-as-Code version mismatch detected
Please check the CI build logs for details and align the documentation version with the Bazel dependency.

@github-actions
Copy link

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

==================
List of all requirements for tools of S-CORE that are not defined or adressed to specific repositories like docs-as-code.

GitHub
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a header or just a first tool, for which requirements exists?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed description

GitHub
^^^^^^

Satisfied
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IF the above is a list, with one tool only, may link from above to the list here, which process requirements the tools is fulffiling

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed description

- Title
- Rationale

* - gd_req__doc_author
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should that not be need, so it can directly be linked to the process requirement?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add links

@PandaeDo PandaeDo requested a review from pahmann as a code owner March 4, 2026 08:36
bazel_dep(name = "score_docs_as_code", version = "3.0.0")
bazel_dep(name = "score_docs_as_code", version = "3.0.1")
bazel_dep(name = "score_process", version = "1.4.3")
git_override(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would prefer we make a new release of process description, instead of using git_override

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I learned that we use override until we made a new release. But this is also possible

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Created:
DEBUG: registry_manager.main Modules to be updated: ['score_process']
 INFO: registry_manager.main ---------------------------------------------------
 ::notice::registry_manager.main Updating score_process from 1.4.3 to 1.4.4

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes we excplitily allowed using git_override now during development, but are (unsure if in 0.7 or 0.8 ref-int release) requiring all of them to be removed in the release that is used in ref-int as they aren't transient.

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.

3 participants