Migrate kaizen distribution to Forgejo
This commit is contained in:
parent
f027ee5492
commit
d4a4560a8d
34 changed files with 324 additions and 195 deletions
|
|
@ -33,7 +33,7 @@ pipx install -e . --force # global pipx install
|
|||
```
|
||||
|
||||
**Consumers (pip install from registry):** see [docs/PACKAGE_RELEASE.md](docs/PACKAGE_RELEASE.md)
|
||||
for Gitea PyPI credentials and `--extra-index-url` install paths.
|
||||
for the Forgejo PyPI `--extra-index-url` install path.
|
||||
|
||||
**Maintainers (release):** `make agents-sync-package` before tagging when `agents/` changes;
|
||||
`make package-check` and the pre-tag checklist in `docs/PACKAGE_RELEASE.md`.
|
||||
|
|
@ -78,7 +78,7 @@ This repository follows PythonVibes best practices:
|
|||
- **Type Checking**: MyPy (`mypy src/`)
|
||||
- **Testing**: Pytest (`pytest`)
|
||||
- **Pre-commit**: `pip install pre-commit && pre-commit install` (see `.pre-commit-config.yaml`)
|
||||
- **CI**: Gitea Actions workflow `.gitea/workflows/ci.yml` runs on push/PR to `main`
|
||||
- **CI**: Forgejo Actions workflow `.forgejo/workflows/ci.yml` runs on push/PR to `main`
|
||||
|
||||
### Agent Development Standards
|
||||
For contributing new agents or improving existing ones:
|
||||
|
|
@ -136,7 +136,7 @@ We welcome bugs, feature ideas, and adoption experience reports.
|
|||
|
||||
- **CLI:** `kaizen-agentic feedback` — lists channels and issue templates
|
||||
- **Guide:** [docs/FEEDBACK.md](docs/FEEDBACK.md)
|
||||
- **Templates:** `.gitea/ISSUE_TEMPLATE/` (bug, feature, general feedback)
|
||||
- **Templates:** `.forgejo/ISSUE_TEMPLATE/` (bug, feature, general feedback)
|
||||
|
||||
For cross-repo coordination between custodian agents, use State Hub messages
|
||||
(`POST /messages/`) — see session protocol in `.claude/rules/session-protocol.md`.
|
||||
|
|
@ -178,7 +178,7 @@ We follow continuous improvement principles:
|
|||
|
||||
### Communication
|
||||
- Be respectful and constructive in all interactions
|
||||
- Use GitHub issues and discussions for project-related communication
|
||||
- Use Forgejo issues for project-related communication
|
||||
- Share knowledge and help other contributors
|
||||
- Follow the project's code of conduct
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue