Repository navigation
Submissions ship in the weekly drop: say so on /submit and in CONTRIBUTING (2.8.7) - #327
Merged
Merged
Conversation
…UTING (2.8.7) Co-authored-by: assaf.barnir <assaf.barnir@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
What kind of change?
content/agents/<slug>.jsonadded)Why
From the Nov 6 run, the weekly content run reviews every open submission, oldest first: issues filed by the form and the MCP
submit_listingtool, and pull requests from forks that add or change a listing. An accepted listing ships in that week's drop, built and checked like every other new listing, and the drop's pull request credits the community pull request it came from. The community pull request is then closed with a link to the live listing. It isn't merged.The site still promised the old flow: /submit said "if it's accepted, we merge it. Merge = live.", and
CONTRIBUTING.mdsaid "a human maintainer merges" and that corrections "merge fast". This PR changes that copy so it says what will actually happen.What this does
app/submit/page.tsx): the pull-request path now says that an accepted listing goes live in the next weekly drop, which credits the pull request, and that the pull request is closed with a link to the listing.CONTRIBUTING.md: the opening says submissions come by pull request, the form or the MCP tool, that each one is reviewed weekly, oldest first, with the decision posted on its issue or pull request, and that accepted listings and corrections go live in the weekly drop. Theverifiednote and "Fix an existing entry" now say "before it ships" and "in the next weekly drop" instead of talking about merging.package.json2.8.7.No behavior changes. Typecheck, lint, 693 unit tests and
validate-content.tspass locally.