nessarandClaude Opus 5.5
f5d592ea5e
Renovate merges these updates with a merge commit once the required check passes, three days after their release. Major updates stay manual. The develop merge allowlist admits the renovate bot for this. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.2 KiB
Agent skills
Issue tracker
Issues and specs live in Gitea Issues; use tea-cli for supported tracker operations. Before tracker work, read docs/agents/issue-tracker.md for commands and API alternatives.
Triage labels
Use the default canonical labels: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. See docs/agents/triage-labels.md.
Domain docs
This is a single-context repo using root CONTEXT.md and docs/adr/. See docs/agents/domain.md.
GitFlow
developis the default integration branch;maincontains releases. Startfeature/*branches from the currentorigin/developand target their PRs todevelop.- Rebase working branches onto the latest
origin/developbefore opening or merging a PR. Ifdevelopadvances, rebase and rerun the PR checks before merging. - Integrate through PRs with successful required checks and merges restricted to designated maintainers through Gitea's merge allowlist. The
developallowlist also admits therenovatebot, which automerges minor, patch, digest, and pin updates oncerequiredpasses; major updates stay manual. Use merge commits (--no-ff) with squashing disabled. Direct and forced pushes tomainanddevelopare forbidden. - Use Conventional Commits for new commits and PR titles.
- Create
release/X.Y.Zfromdevelopandhotfix/X.Y.Zfrommain. Onlyrelease/*andhotfix/*PRs targetmain. Merge each release or hotfix into bothmainanddevelop, keeping its branch until both PRs are merged. - Use merges and back-merges for releases and hotfixes. Never rebase
main,develop, or a frozen release branch.
The CI workflow is .gitea/workflows/ci.yml. Activation is tracked in Gitea issue #268; Actions is enabled with owner approval, and the migration gate stays required until live workflow validation and merge-message review. Before changing CI, image publication, or activation settings, read Gitea Actions.
Before preparing a release or hotfix, creating a tag, or changing image publication, read GitFlow and releases for package versions, explicit stable tags, and image promotion.