Skip to content

docs: require milestones when creating issues #171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
enaboapps merged 1 commit into from
Sep 14, 2026
Merged

docs: require milestones when creating issues #171

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ The application uses TypeScript, React 19, React Native 0.86, Expo Router, and n

Follow this workflow for every change:

1. Create a GitHub issue that defines the change and acceptance criteria.
1. Create a GitHub issue that defines the change and acceptance criteria. Never create a GitHub issue without a milestone. Select or create the appropriate milestone first and include it in the issue creation request; assigning it afterward is not allowed. This applies to every issue, including bugs, chores, release preparation, and follow-up work. Verify the milestone on the created issue before continuing.
2. Fetch the intended base branch and create a focused `codex/<description>-<issue>` branch from it. Use `main` unless the issue or user identifies another base.
3. Inspect neighboring code, tests, documentation, and configuration before editing.
4. Make the smallest coherent change that satisfies the issue.
Expand Down