merge: IT-628 RabbitMQ worker, contracts, usage UI in channels screen #16
@@ -0,0 +1,27 @@
|
||||
# HrynCo Notification Service Agent Rules
|
||||
|
||||
## Git workflow
|
||||
|
||||
- Treat `main` as the only default and integration branch for this repository.
|
||||
- Start every task branch from the latest `origin/main`.
|
||||
- Before creating a task branch, fetch the remote, switch to `main`, and fast-forward it from `origin/main`.
|
||||
- Create the task branch only after confirming that local `main` matches `origin/main`.
|
||||
- Open pull requests from the task branch into `main`.
|
||||
- Do not use `development` as the base or pull-request target for new work in this repository.
|
||||
- Do not commit, push, publish, deploy, or merge unless the repository owner explicitly requests that step.
|
||||
|
||||
Recommended branch preparation:
|
||||
|
||||
```text
|
||||
git fetch origin
|
||||
git switch main
|
||||
git pull --ff-only origin main
|
||||
git switch -c <task-branch>
|
||||
```
|
||||
|
||||
## Delivery
|
||||
|
||||
- Keep changes focused and preserve backward compatibility where practical.
|
||||
- Update the matching repository documentation when behavior, contracts, configuration, routing, or workflows change.
|
||||
- Run the solution build and relevant tests before handoff.
|
||||
- Use Conventional Commit messages with a lowercase subject and finish the commit body with `Ref: <issue-id>` when an issue exists.
|
||||
Reference in New Issue
Block a user