Repository navigation
docs(roadmap): add #367 to the M2 milestone row - #368
Merged
Merged
Conversation
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.
Summary
Adds #367 (let a CI pass on the final head satisfy a required local
unverifiedcheck) to the M2 row of the milestone table indocs/ROADMAP_V2.md, marked as conditional on #329. The issue is in M2 with labelP2and on the "Code Cycle Toolkit roadmap" project, asAGENTS.mdrequires; a milestone content change updates the table in the same pull request.Documentation
Only the milestone table changes; no behaviour, command, schema or configuration key.
README.mdis unaffected.Verification
python3 scripts/validate-package.pypasses.Refs #367. It does not close #367, which is implementation work still to do.