Conversation
|
|
|
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 |
There was a problem hiding this comment.
Is this a header or just a first tool, for which requirements exists?
There was a problem hiding this comment.
Changed description
| GitHub | ||
| ^^^^^^ | ||
|
|
||
| Satisfied |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Changed description
| - Title | ||
| - Rationale | ||
|
|
||
| * - gd_req__doc_author |
There was a problem hiding this comment.
should that not be need, so it can directly be linked to the process requirement?
| 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( |
There was a problem hiding this comment.
would prefer we make a new release of process description, instead of using git_override
There was a problem hiding this comment.
I learned that we use override until we made a new release. But this is also possible
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Available for you, https://github.com/eclipse-score/bazel_registry/pull/322/changes
There was a problem hiding this comment.
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.
Create of initial list tool requirements of process requirements that will not be solved by docs-as-code