Skip to content

docs(workflow): use GitHub Issues for internal work - #6

Merged
ahilles107 merged 1 commit into
mainfrom
fix/github-issue-tracking
Sep 8, 2026
Merged

ahilles107 merged 1 commit into
mainfrom
fix/github-issue-tracking

Conversation

@ahilles107

@ahilles107 ahilles107 commented Sep 8, 2026

Copy link
Copy Markdown
Owner

What

Use GitHub Issues for all Gravity tasks, including internal maintainer work. Add repository instructions for coding agents, explicitly overriding inherited Linear requirements, and align contributor and release guidance with GitHub issue references.

Fixes #5. Follow-up to merged #4.

Why

The public contributor guide already directs users to GitHub, while shared agent guidance still requires Linear. Repository-local instructions make the workflow consistent without changing other projects' settings. Existing private backlog items require a separately scoped disclosure review before migration.

How tested

  • All six required hosted checks passed, including visual CI.
  • Reviewed tracked guidance and workflows for Linear dependencies; retained the Linear-specific secret detector.
  • Documentation links and git diff checks passed. Gitleaks on the feature commit found no secrets.
  • Full local verification passed through native Clippy. Native test compilation failed with No space left on device; local visual tests were not reached. Native tests passed in the preceding skills audit; this change only edits documentation.

Documentation only; no release or production configuration change.

@ahilles107
ahilles107 merged commit bab1d55 into main Sep 8, 2026
6 checks passed
@ahilles107
ahilles107 deleted the fix/github-issue-tracking branch September 8, 2026 04:58
ahilles107 added a commit that referenced this pull request Sep 10, 2026
Patch bump: everything since v0.12.4 is a fix or docs/tooling change with
no new or removed user-facing surface — the terminal keeps its scroll
position across bot switches (#7), the contributor skills were made safe
and portable (#4), and internal work moved to GitHub Issues (#6).
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.

Use GitHub Issues for internal Gravity work

1 participant