Repository navigation
docs(specs): use the empty line term in cycle 001 - #273
Merged
Merged
Conversation
The terminology lint of the whole codebase requires the empty line term over blank line.
The temporary path in the Path row contains the test name and matched first.
This file contains hidden or 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
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.
The whole-codebase lint run on master after the merge of the first cycle flagged the cycle 001 artifacts: the terminology rule of the repository requires the term empty line over blank line (21 findings across
spec.md,plan.md, andtasks.md). The pull request runs lint the changed files only, so the findings surfaced only in the master run.This change is a wording correction only. The findings, the decisions, and the outcomes recorded in the cycle stay unchanged. Every occurrence of the term in the three artifacts now reads empty line.