Governance: auto-label data submissions community + document contribution lanes#53
Merged
Jose-Gael-Cruz-Lopez merged 2 commits intoJul 4, 2026
Merged
Conversation
Every add/verify/edit/close/photo submission now carries the community label, keeping the data lane visually separate from invited-dev (frontend/backend/infra) issues. Existing automation labels (new_opportunity, auto_extract, etc.) are preserved. The 'Other' catch-all is intentionally left unlabeled. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Adds a 'Two Ways to Contribute' section distinguishing open data contributions (anyone, via issues) from software work (invited developers). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What & why
Codifies the data-vs-dev contribution model so the two lanes are obvious and self-sorting.
1. Auto-apply the
communitylabel to data-lane issue templatesEvery data submission now opens pre-labeled
community, keeping it visually separate from invited-developer work (frontend/backend/infra/security/bug).new_opportunity,auto_extractcommunitynew_opportunitycommunitynew_opportunity,quick_addcommunityedit_opportunitycommunityclose_opportunitycommunitygallerycommunityauto_extract.yml/contribution_approved.ymltriggers (which key offapproved+auto_extract/new_opportunity/close_opportunity) are unaffected by the extra label.Otheris intentionally left unlabeled (catch-all for questions / bug reports / dev requests).2. CONTRIBUTING.md — "Two Ways to Contribute"
Documents the model in words: add hackathons (anyone, via issues, no repo access) vs. work on the software (invited developers; others propose via fork + PR).
Notes
communitylabel already exists on the repo and has been applied to the current data issues (Add: AI Hacks (LA Hacks) #38, New deadlines needed #39).mainis protected against force-push/deletion, and the dev/app issues (🌍 Epic: HackHQ interactive globe site #10–Infra: Cloudflare Pages deployment + Supabase env + domain #20, [Critical] Security: GitHub Actions command & script injection via untrusted issue content #41–[Low] Tech-debt: code quality & maintainability cleanup (checklist) #51) are locked to collaborators-only.Test / verify after merge
community.🤖 Generated with Claude Code