chore(submissions): auto outreach run 2026-07-31 01:17 - #4
Open
bucabay wants to merge 3 commits 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.
…log run 2026-07-30
- Opened 2 external PRs (cap <=3): * bytefer/awesome-nextjs #23 (## SaaS) — same maintainer that merged our shadcn-ui #29 * semlinker/awesome-typescript #177 (## TypeScript Starters/Boilerplates) — NEW 4038★ reach - 0 emails (all venues PR/form-based; no public contact email inviting pitches) - brillout/awesome-react-components (48k★) flagged MANUAL: not merging outside PRs + remove-rule - 6 pending PRs unchanged (bytefer/shadcn #29 already LIVE)
|
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-31 01:17 UTC (token healthy, run #2 since the 07-29 fix).
Researched
GitHub search sweep across awesome-{nextjs,boilerplate,react,typescript,shadcn,tailwind,drizzle,vercel,turborepo,postgres,fullstack,startup,stripe,auth} + opensource-boilerplate. Each candidate verified: not archived, pushed <6mo, actively merges outside PRs, MIT-compatible, FREE, fitting section, no AI-PR ban. Nothing already in SUBMISSIONS.md.
PRs opened (2 / cap 3)
## SaaS, appended after Next Money. Same maintainer that already merged our bytefer/awesome-shadcn-ui #29 → highest merge-probability venue this run. 71★.## TypeScript Starters/Boilerplates, appended at end per their guide. NEW actionable find: 4038★, actively merges add-PRs (6 of last 8), no AI ban. (Prior runs only had the archived dzharii/awesome-typescript.)Held the 3rd PR slot for quality — nothing else met the bar.
Emails sent (0 / cap 5)
Re-confirmed: every submission venue is PR-based or form-only (dev/JS/React/Next weeklies, react.email, smashingmagazine, css-tricks = forms/editorial). No venue exposes a public contact email inviting tool pitches → cold-emailing awesome-list maintainers (who explicitly prefer PRs) would be non-compliant spam. Documented, not acted.
Flagged for human (do NOT auto-act)
### Boilerplatefit, but last 8 closed PRs all closed-unmerged (maintainer stopped merging outside PRs) + CONTRIBUTING requires "YOU MUST REMOVE one un-awesome component in any PR" (a clean one-line add is non-compliant). Worth a human-curated remove-a-dead-entry + add-ours PR later.Pending PRs (unchanged)
✅ bytefer/awesome-shadcn-ui #29 — LIVE (first listing). Awaiting merge: SaaS4Devs #54, xcomptek #222, EinGuterWaran #52, unicodeveloper #536, birobirobiro #554.
Note
origin/mainis still stale (94 lines) — prior wrap-up PRs #1/#2/#3 are unmerged, so this branch builds onsubmissions/auto-20260730-1717(full 141→162-line SSOT) to preserve the accumulated research + this run. Merging this (or a prior wrap-up) lands everything to date.