chore(submissions): auto outreach run 2026-07-31 21:26 - #6
Open
bucabay wants to merge 2 commits into
Open
Conversation
Reconciled the submission log against actual @bucabay PRs on GitHub: recorded 7 previously-unlogged submissions and marked bytefer/awesome-shadcn-ui (PR #29) as our first LIVE listing. Added a 'Researched & skipped' table so future runs don't re-evaluate dead/poor-fit venues, and deferred officialrajdeepsingh/awesome-nextjs (100-star bar; repo at 0 stars). No new external PRs or emails this run — all strong git-PR venues were already in flight (8 open / 1 live) and no appropriate non-spammy email venue existed.
Research-only run: no new qualifying git-PR or email venues found. Recorded 11 newly-researched-and-skipped venues (with live-verified star count, last push, and merge cadence) so future runs don't re-research. - 0 external PRs opened (well of high-quality awesome-lists is tapped; every fresh candidate failed freshness/fit/merge/license gate) - 0 emails (no email-channel venues; template dirs are form-based; cold-nudging maintainers = pestering, not outreach) - 1 MANUAL flag: Built at Lightspeed (HTTP 429, unverifiable, marginal fit) Based on submissions/auto-2026-07-31-1717 (PR #5) — main is stale (last merged 2026-07-19); 5 prior run-PRs remain open/unmerged.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Automated submission-outreach run · 2026-07-31 21:26 UTC.
TL;DR
Research-only run — no new qualifying venues. The well of high-quality git-PR awesome-lists
is largely tapped (9 already submitted). Recorded this run's findings so future runs don't
re-research them.
What was added
New "Researched & skipped (2026-07-31 run #2)" subsection in
docs/SUBMISSIONS.md(11 rows). Highlights of why nothing was actionable:
🚩 Flagged for a human
(rate-limited), couldn't verify reachability/submit flow; marginal Jamstack fit. Verify manually
before pursuing.
Why no emails
No email-channel venues exist this run — awesome-lists are PR-based and the template directories
(HTMLrev / Tailkits / Built at Lightspeed) are form-based. Cold-emailing maintainers to nudge the
8 pending awesome-list PRs is pestering, not outreach, so it was deliberately not done.
mainis stale: last merged2026-07-19, only 2 submission-log entries. 5 prior run-PRs(#1–#5) are open and unmerged. This PR is therefore stacked on the latest accumulated state
(
submissions/auto-2026-07-31-1717= PR #5, a full reconcile) + this run's delta.Recommended: merge this PR (it contains PR #5's reconcile + this run), then close the
superseded older run-PRs (#1–#5). That brings
mainfully up to date in one merge.Diff vs
main: +55/-3 indocs/SUBMISSIONS.md(single file, docs-only).