Repository navigation
docs: refresh issue links after the Go rewrite - #123
Merged
Merged
Conversation
Point recruiting to the ongoing onboarding discussion and backend tracking to release readiness. Signed-off-by: debpalash <4178343+debpalash@users.noreply.github.com>
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 Go rewrite RFC #33 is now closed as implemented. Point the README’s co-maintainer call to the ongoing onboarding discussion #122, and point backend tracking to the release-readiness checklist #120.
Validation: both new issue targets exist and are open; the diff changes only two README link destinations and their labels. Sponsor content and demo sections are preserved. No application tests are needed for this link-only documentation change.