Repository navigation
tooling: Correct Stakeholders' requirements ids to be meaningful. - #477
Conversation
0624ae1 to
aa3346e
Compare
|
Thanks for creating the PR, looks good. So I think we need also an exception for the "req contains feature" check for the stakeholder requirements. Can you include this change into this PR? |
aa3346e to
d8247f7
Compare
|
@hoe-jo I updated the check please review it to see if it's exactly doing what you are expecting as we only have 24 remaining errors now. |
dacef95 to
32ecfde
Compare
|
Currently I only see 3 warnings: fastbuild/bin/docs/_docs/_sources/docs/requirements/tool/index.rst:25: WARNING: Need 'tool_req__tool__bazel_build' has unknown outgoing link 'stkh_req__integration__int_multi_repo' in field 'satisfies' [needs.link_outgoing] requirements/tool/index.rst:25: WARNING: tool_req__tool__bazel_build: has a parent requirement(s): requirements/tool/index.rst:25: WARNING: tool_req__tool__bazel_build: has a valid status but one of its parents: And this turns out to be a false linkage the id of the stkh_req was defined as stkh_req__integration__multi_repo_ Can you please correct it? |
32ecfde to
5406bc6
Compare
|
@hoe-jo I corrected the last stkh_req error. We just have 21 errors related to gd_ now |
|
The created documentation from the pull request is available at: docu-html |
Replace all IDs of stakeholders requirements and their references that include numbers with meaningful IDs. Also-by: Aymen Soussi aymen.soussi@expleogroup.com
5406bc6 to
e445299
Compare
Replace all IDs of stakeholders requirements that include numbers with meaningful IDs.
Also-by: Aymen Soussi aymen.soussi@expleogroup.com
Related to: #282