Repository navigation
data: drop the next steps of three blockers that #66 resolved - #81
Merged
Merged
Conversation
pr-425, siglongjmp and pr-1922 are fixed by merged PRs since #66, but their drawers still asked to land #425, to open a PR from #1578's branch and to submit #1922 again.
github-actions
Bot
added
the
data-correction
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
1 participant
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.
What
Since #66, merged PRs fix
pr-425,siglongjmpandpr-1922. Their drawers still showed a next step asking to land #425, to open a PR from #1578's branch and to submit #1922 again. This drops those threenextlines. Nothing else changes.Source
Checklist
main, ormainplus PRs that are merged nowtests/(no rule change)ruff check .andruff format --check .pass locallyweb/: noweb/changenextfields are gone fromroadmap.json