Move results format specification out of L2 metadata level #3421
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
happz
requested review from
psss,
lukaszachy,
thrix and
janhavlin
as code owners
therazix
approved these changes
Dec 17, 2024
seberm
approved these changes
Jan 9, 2025
lukaszachy
approved these changes
Jan 15, 2025
happz
added
the
status | ready for merge
|
@happz, could you please rebase? |
happz
force-pushed
the
spec-results-more-visible
branch
from
8bbfbfe to
9813083
Compare
Done. |
This should make the result format documentation more visible, more prominent. It is important part of tmt integration, and deserves its own place in specification, similar to what HW requirements have.
psss
force-pushed
the
spec-results-more-visible
branch
from
4d18fe9 to
d99a07a
Compare
|
Documentation change, core tests passed, merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should make the result format documentation more visible, more prominent. It is important part of tmt integration, and deserves its own place in specification, similar to what HW requirements have.
Pull Request Checklist