[BOUNTY $20] No issue tracker usage — 30 repos, 0 issues — problems live only in sessions#2
Open
qlufiq-collab wants to merge 1 commit into
Conversation
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
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.
Summary
Add issue tracking infrastructure to flux-chamber: standardized label definitions, issue templates (bug report, enhancement, bounty), a GitHub Actions workflow to sync labels automatically, and a CONTRIBUTING.md documenting the issue tracking workflow and bounty process.
Changes
.github/labels.yml— Declarative label definitions (bug, enhancement, bounty, documentation, wontfix, meta, good first issue, help wanted) matching the standard required across all @COMMENCINGTHESCOURGE repos.github/ISSUE_TEMPLATE/bug_report.md— Structured bug report template.github/ISSUE_TEMPLATE/enhancement.md— Feature request template.github/ISSUE_TEMPLATE/bounty.md— Bounty task template with acceptance criteria section.github/ISSUE_TEMPLATE/config.yml— Template chooser configuration.github/workflows/label-sync.yml— GitHub Actions workflow that syncs labels fromlabels.ymlon push to main (uses EndBug/label-sync)CONTRIBUTING.md— Documents label standards, issue filing guidelines, bounty workflow, and development setupTest Plan
npm test→ 47 tests pass (no regressions, changes are infrastructure-only)npm run lint→ No new errors (lint scope issrc/only; all new files are in.github/and repo root)Notes
This PR addresses the flux-chamber portion of the meta-task. The
labels.ymlfile serves as the canonical label set that can be copied to sibling repos (aetherion-continuum, hyperpoly-terrain, trench-builder) along with the same workflow. Theautomation_audit.pyfindings referenced in the issue are not present in this repository — filing those as individual issues is a separate step that requires access to that file's output.Closes #1