Skip to content
Merged
Changes from all commits
Commits
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
10 changes: 8 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ The account-wide Codegeist policies apply alongside this repository-specific
guide:

- [Contribution policy](https://github.com/codegeist-ai/.github/blob/main/CONTRIBUTING.md)
- [GitHub account and repository model](https://github.com/codegeist-ai/.github/blob/main/GITHUB_ACCOUNT_MODEL.md)
- [Code of Conduct](https://github.com/codegeist-ai/.github/blob/main/CODE_OF_CONDUCT.md)
- [Security policy](https://github.com/codegeist-ai/.github/blob/main/SECURITY.md)
- [Support guide](https://github.com/codegeist-ai/.github/blob/main/SUPPORT.md)
Expand All @@ -29,7 +30,10 @@ unclear.
## Source Workflow

1. Find or open a repository [Issue](https://github.com/codegeist-ai/codegeist-agent-kit/issues) and check the [Codegeist roadmap](https://github.com/users/codegeist-ai/projects/1).
2. Use the linked specification under [`docs/tasks/`](docs/tasks/README.md) when one exists.
2. An Issue labeled `status:ready` must link its canonical specification under
[`docs/tasks/`](docs/tasks/README.md). For a small unplanned fix, a maintainer may
confirm that no new task is needed; state the reason in the pull request. Always
use an existing task when one defines the work.
3. Create a topic branch from the source `main` branch.
4. Edit the source paths at the repository root. The generated `release` branch and consuming `.opencode/` checkouts are distribution outputs, not implementation targets.
5. Run the normal repository check:
Expand All @@ -38,7 +42,9 @@ unclear.
task test
```

6. Open a pull request that links the Issue and local task, summarizes the source and release impact, and reports verification.
6. Open a pull request that links the Issue and applicable local task, summarizes
the source and release impact, and reports verification. If no new task was
required, state `No local task needed:` and the maintainer-approved reason.

`task test` copies and validates the release bundle without creating commits,
publishing a release, or updating submodules. Release publication through
Expand Down