This repository was archived by the owner on Sep 7, 2026. It is now read-only.
docs: retire ReplyQueue and preserve historical guidance - #1
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
ReplyQueue is retired and its Chrome Web Store listing has been unpublished. Add retirement notices to README.md and CONTRIBUTING.md, remove store installation links, and preserve source setup instructions and the roadmap as historical documentation for independent forks.
Validation: reviewed the diff, ran git diff --check, and verified retirement notices, removal of store links, and relative documentation links. Application tests were not run because only Markdown documentation changed.
The Semgrep CI check reported two findings in unchanged files: actions/checkout uses a mutable v4 tag in .github/workflows/security.yml, and an npm release-age rule flags .npmrc, which currently configures pnpm minimum-release-age=4320. These existing configuration findings are outside this documentation change.