Adds OpenFastTrace for requirements tracking #11710
Merged
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
koppor
added
the
type: code-quality
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
…dd-open-fast-trace # Conflicts: # docs/requirements/ai.md # docs/requirements/index.md
…dd-open-fast-trace
koppor
added
the
status: ready-for-review
|
The build for this PR is no longer available. Please visit https://builds.jabref.org/main/ for the latest build. |
koppor
changed the title
6 tasks
calixtus
approved these changes
Sep 8, 2024
leaf-soba
pushed a commit
to leaf-soba/jabref
that referenced
this pull request
Sep 11, 2024
* Initial requirement * Initial requirement * Add OpenFastTrace * Fix linting * Remove wrong disable rule
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 introduces OpenFastTrace to JabRef. One can state requirements - and at the Java classes, where they are implemented. And a CI check is running to check consistency.
This is especially important if there are not tests, but refactoring going on. (My example was the refactoring of the AI chat tab)
Real-world examples in the Markdown documentation cannot be used due to itsallcode/openfasttrace#280
Mandatory checks
CHANGELOG.mddescribed in a way that is understandable for the average user (if applicable)