chore(submissions): auto outreach run 2026-07-29 17:17 - #2
Open
bucabay wants to merge 1 commit into
Open
Conversation
GH_TOKEN works again (was HTTP 401 since 2026-07-19, 6 runs / 10 days). This run opened 3 external PRs (cap <=3), each a clean one-line entry added from a fork, entry verified absent + no AI-PR ban: - xcomptek/awesome-saas-boilerplates #222 (## Next.js, alphabetical) - EinGuterWaran/awesome-opensource-boilerplates #52 (### React & Next.js) - bytefer/awesome-shadcn-ui #29 (## Saas table row) officialrajdeepsingh/awesome-nextjs downgraded to MANUAL: its CONTRIBUTING requires >=100 stars and bans "new projects"; mailkite/saas-startup is 0 stars / 2 weeks old (fails both; escape clause => human pitch only). Also lands all previously-blocked research onto origin/main (origin was stale at the 94-line 07-17 doc; the staged venues + ready-to-paste entries had survived only on local branches through the 401 outage). 0 emails (all awesome-lists are PR-based; dev newsletters use submission forms, so cold-emailing editors to pitch a 0-star repo is non-compliant). Full details in docs/SUBMISSIONS.md submission log.
|
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.
Autonomous submission-outreach run · 2026-07-29 17:17 UTC.
⭐ Headline: the
GH_TOKENblock is overThe token had been HTTP-401 since 2026-07-19 — 6 consecutive runs / 10 days with zero
external action possible. This run it works again (login
bucabay, scopes incl.repo/workflow),so I finally shipped the staged work.
External PRs opened (3 / 3 — cap reached)
Each is a clean one-line entry added from a fork, with the entry verified absent and no AI-PR ban:
## Next.js, alphabetical (LaunchFa.st ↔ Mkdirs)### React & Next.js, appended## Saastable, appended rowEmails sent: 0
All awesome-lists are PR-based (no contact email). Dev newsletters (JS / React / Next.js Weeklies)
expose only submission forms, so cold-emailing their editors to pitch a 0-star, 2-week-old repo
would bypass their process and read as spam — not compliant. No email venue met the bar.
Flagged for human (no auto-action)
CONTRIBUTING.mdrequires≥100 stars and bans "new or unreleased projects";
mailkite/saas-startupis 0★,created 2026-07-15 (fails both). There's an escape clause ("if unique, you may still submit
for review") — recommend Gabe pitch the self-contained-auth uniqueness by hand, ideally once
stars grow. (This corrects a prior run that ranked it DRY RUN chore(submissions): auto outreach run 2026-07-19 13:16 #1 without checking our own star count.)
pushed_at2026-03-24); consider closing.safe to close.
Research this run
GitHub search across nextjs / saas / shadcn / tailwind / drizzle / turborepo / typescript / postgres.
No new strong venue — the niche is saturated: candidates were already-logged, dormant (>6mo),
wrong-ecosystem (Flutter/Svelte), archived (
dzharii/awesome-typescript), or ≤28★ (shadverse,28★ / 1 PR ever, skipped as negligible).
What else this PR does
origin/mainwas stale at the 94-line 07-17 doc (every prior push 401'd). This PR also landsall the accumulated research (staged venues, ready-to-paste entries, pending-PR intel) that had
survived only on local branches through the outage. See the submission log in
docs/SUBMISSIONS.md.