Skip to content

feat: add GitHub setup script and 100-star Sponsors watcher - #56

Merged
jamesconwaydev merged 4 commits into
mainfrom
task-17a-github
Nov 6, 2026
Merged

jamesconwaydev merged 4 commits into
mainfrom
task-17a-github

Conversation

@jamesconwaydev

Copy link
Copy Markdown
Collaborator

What's in here:

  • scripts/admin/setup_github.py sets up the GitHub side of the project: labels, org issue types and issue fields, the DevStream Roadmap project with its fields and views, the three milestones, and the backlog issues with their epics, blockers and project fields. It also sets the repo description, the org profile and the security defaults for new repos. It looks before it writes, so running it again changes nothing, and on issues that already exist it only fills in what's empty.
  • scripts/stars.py and .github/workflows/stars.yml check the star count once a day. At 100 stars they open one issue saying it's time to turn on GitHub Sponsors, with the FUNDING.yml steps. Below 100 they do nothing.
  • .github/ISSUE_TEMPLATE/other.md gives the community profile a Markdown template to find. It doesn't count issue forms, which is why it showed issue_template: false.
  • .github/dependabot.yml labels Dependabot PRs dependencies only, so ecosystem labels like javascript stop reappearing.

Tests: python3 -m unittest discover -s scripts -t . passes, and action-validator passes on stars.yml.

Part of the v0.1 launch.

setup_github.py sets labels, issue types and fields, the roadmap
project, milestones and the backlog, and is safe to re-run. stars.yml
opens one issue when the repo reaches 100 stars. A Markdown issue
template lets the community profile see our issue templates, and
Dependabot now uses only the dependencies label.
Only duplicate, invalid, question and wontfix are ever deleted, and
only when no issue in any state uses them. A skipped optional step
now prints a loud summary and exits 2. The new-repo security defaults
turn on private vulnerability reporting, the seed issue no longer
cites a subcommand that doesn't exist yet, and stars.py raises when
the issue search returns nothing.
A 403 asking for GitHub Team means the feature isn't on our plan, not
that the run broke, so it no longer makes the script exit 2. Any other
error still does. The step stays so it works if the org upgrades.
@jamesconwaydev
jamesconwaydev merged commit 7fb408c into main Nov 6, 2026
8 checks passed
@jamesconwaydev
jamesconwaydev deleted the task-17a-github branch November 6, 2026 02:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant