Skip to content

[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
COMMENCINGTHESCOURGE:mainfrom
qlufiq-collab:bounty/COMMENCINGTHESCOURGE/flux-chamber-1
Open

[BOUNTY $20] No issue tracker usage — 30 repos, 0 issues — problems live only in sessions#2
qlufiq-collab wants to merge 1 commit into
COMMENCINGTHESCOURGE:mainfrom
qlufiq-collab:bounty/COMMENCINGTHESCOURGE/flux-chamber-1

Conversation

@qlufiq-collab

Copy link
Copy Markdown

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 from labels.yml on push to main (uses EndBug/label-sync)
  • CONTRIBUTING.md — Documents label standards, issue filing guidelines, bounty workflow, and development setup

Test Plan

  • npm test → 47 tests pass (no regressions, changes are infrastructure-only)
  • npm run lint → No new errors (lint scope is src/ only; all new files are in .github/ and repo root)
  • Label sync workflow validated against EndBug/label-sync v2 schema
  • Issue templates validated against GitHub's YAML frontmatter spec

Notes

This PR addresses the flux-chamber portion of the meta-task. The labels.yml file serves as the canonical label set that can be copied to sibling repos (aetherion-continuum, hyperpoly-terrain, trench-builder) along with the same workflow. The automation_audit.py findings 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

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.

[BOUNTY $20] No issue tracker usage — 30 repos, 0 issues — problems live only in sessions

1 participant