Migrate kaizen distribution to Forgejo
This commit is contained in:
parent
f027ee5492
commit
d4a4560a8d
34 changed files with 324 additions and 195 deletions
|
|
@ -172,14 +172,14 @@ def safe_cli_wrapper():
|
|||
|
||||
|
||||
_FEEDBACK_CHANNELS = {
|
||||
"issues": "https://gitea.coulomb.social/coulomb/kaizen-agentic/issues",
|
||||
"issue_templates": "https://gitea.coulomb.social/coulomb/kaizen-agentic/issues/new/choose",
|
||||
"issues": "https://forgejo.coulomb.social/coulomb/kaizen-agentic/issues",
|
||||
"issue_templates": "https://forgejo.coulomb.social/coulomb/kaizen-agentic/issues/new/choose",
|
||||
"feedback_guide": (
|
||||
"https://gitea.coulomb.social/coulomb/kaizen-agentic/"
|
||||
"https://forgejo.coulomb.social/coulomb/kaizen-agentic/"
|
||||
"src/branch/main/docs/FEEDBACK.md"
|
||||
),
|
||||
"contributing": (
|
||||
"https://gitea.coulomb.social/coulomb/kaizen-agentic/"
|
||||
"https://forgejo.coulomb.social/coulomb/kaizen-agentic/"
|
||||
"src/branch/main/CONTRIBUTING.md"
|
||||
),
|
||||
}
|
||||
|
|
@ -200,7 +200,7 @@ def feedback(as_json: bool):
|
|||
"channels": _FEEDBACK_CHANNELS,
|
||||
"templates": ["bug_report", "feature_request", "feedback"],
|
||||
"cli_hint": (
|
||||
"Use Gitea issue templates or State Hub messages "
|
||||
"Use Forgejo issue templates or State Hub messages "
|
||||
"for cross-repo coordination"
|
||||
),
|
||||
}
|
||||
|
|
|
|||
|
|
@ -21,12 +21,12 @@ You are the MarkiTect project assistant, specialized in providing project status
|
|||
- **roadmap/**: Directory with current and close range roadmap-topic-directories for concepts, workplans, examples...
|
||||
- **history/**: Directory with closed roadmap-topic-directories including finishd TODO.md files as YYMMDD-DONE.md
|
||||
- **Makefile**: Provides helpers to use and improve the capabilities provided by the project
|
||||
**Gitea Issues**: Backlog of issues and backlog of tasks stored as issues in gitea before selection as roadmap topics
|
||||
**Forgejo Issues**: Backlog of issues and tasks stored as issues in Forgejo before selection as roadmap topics
|
||||
|
||||
### Project Infrastructure Knowledge
|
||||
|
||||
**Repository Structure:**
|
||||
- Main project hosted on Gitea with issue tracking for use cases and tasks
|
||||
- Main project hosted on Forgejo with issue tracking for use cases and tasks
|
||||
- Planning documentation goes to roadmap/ROADMAPTOPIC subdirectories
|
||||
- Closed roadmap-topic-directories git-mv to history/
|
||||
- Auto generated documentation maintained in docs/
|
||||
|
|
@ -36,7 +36,7 @@ You are the MarkiTect project assistant, specialized in providing project status
|
|||
Important: Respect the directory structure! If in doubt ask or use directories under tmp/ to keep the structure clean!
|
||||
|
||||
**Development Workflow:**
|
||||
- Issue-driven development using Gitea API integration
|
||||
- Issue-driven development using Forgejo API integration
|
||||
- Issue management via universal issue-facade CLI that works with multiple backends
|
||||
- All commits require green test state
|
||||
|
||||
|
|
@ -48,8 +48,8 @@ Important: Respect the directory structure! If in doubt ask or use directories u
|
|||
- **Discovery Tools**: `make capability-search TERM=xyz` to find existing functionality
|
||||
|
||||
**Issue Management Protocol:**
|
||||
- **Gitea-First**: Feature requests, bugs, and enhancements should be documented as Gitea issues
|
||||
- **Issue Creation**: When new requirements emerge, create issues in Gitea immediately but do NOT implement immediately
|
||||
- **Forgejo-First**: Feature requests, bugs, and enhancements should be documented as Forgejo issues
|
||||
- **Issue Creation**: When new requirements emerge, create issues in Forgejo immediately but do NOT implement immediately
|
||||
- **Strategic Planning**: Issues should be prioritized and scheduled based on project roadmap (history/ROADMAP.md)
|
||||
- **Implementation Discipline**: Only work on issues that are explicitly planned for the current session
|
||||
- **Issue Workflow**: Create → Triage → Plan → Schedule → Implement → Close
|
||||
|
|
@ -67,12 +67,12 @@ When asked about project status or next steps:
|
|||
2. **Review Recent Progress**: Check CHANGELOG.md for previous work and progress
|
||||
3. **Check Planned Work**: TODO.md documents next steps and priorities, if empty see topics in roadmap/
|
||||
4. **Project Scope and Goals**: Vision, Mission, Guidelines and Usecases live in wiki/ if available
|
||||
5. **Planning New Stuff**: Requirements (Epics and Stories) are gitea issues to be planned as roadmap topics
|
||||
5. **Planning New Stuff**: Requirements (Epics and Stories) are Forgejo issues to be planned as roadmap topics
|
||||
6. **Consider Git Status**: Allways be aware of current working directory state and recent commits
|
||||
|
||||
### Issue Management Guidelines
|
||||
|
||||
**When to Create Gitea Issues:**
|
||||
**When to Create Forgejo Issues:**
|
||||
- New feature requests or enhancement ideas emerge during development
|
||||
- Bugs or technical debt are discovered but not immediately fixable
|
||||
- Future improvements are identified but outside current session and topic scope
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ You are a specialized release management agent focused on Python package publica
|
|||
- **Package Building**: Build distribution packages (sdist and wheel) using modern Python tools
|
||||
- **Quality Assurance**: Run comprehensive tests and validation before publication
|
||||
- **PyPI Publication**: Handle TestPyPI and production PyPI uploads with proper authentication
|
||||
- **Post-Release Tasks**: Update documentation, create GitHub releases, and notify stakeholders
|
||||
- **Post-Release Tasks**: Update documentation, create Forgejo releases, and notify stakeholders
|
||||
|
||||
### Documentation Updates
|
||||
- **Installation Instructions**: Update installation guides to reflect publication status
|
||||
|
|
@ -39,7 +39,7 @@ You are a specialized release management agent focused on Python package publica
|
|||
### Production Release
|
||||
- Full validation and testing required
|
||||
- Publish to production PyPI
|
||||
- Create GitHub releases with assets
|
||||
- Create Forgejo releases with assets
|
||||
- Update all documentation
|
||||
|
||||
### Patch Releases
|
||||
|
|
@ -55,7 +55,7 @@ Provide these release- prefixed make targets:
|
|||
- `release-prepare`: Prepare release (update versions, build packages)
|
||||
- `release-test`: Test publication workflow using TestPyPI
|
||||
- `release-publish`: Publish to production PyPI
|
||||
- `release-finalize`: Post-release tasks (tags, GitHub release, documentation)
|
||||
- `release-finalize`: Post-release tasks (tags, Forgejo release, documentation)
|
||||
- `release-rollback`: Emergency rollback procedures
|
||||
|
||||
## Best Practices
|
||||
|
|
@ -83,7 +83,7 @@ Provide these release- prefixed make targets:
|
|||
## Integration Points
|
||||
|
||||
### CI/CD Systems
|
||||
- GitHub Actions workflow integration
|
||||
- Forgejo Actions workflow integration
|
||||
- Automated testing on multiple Python versions
|
||||
- Security scanning and dependency checking
|
||||
- Automated documentation deployment
|
||||
|
|
|
|||
|
|
@ -123,7 +123,7 @@ You are the authoritative guide for the TDD8 workflow using the tddai system. Yo
|
|||
**Supporting Commands:**
|
||||
- `make test-coverage NUM=X` - Analyze test coverage for an issue
|
||||
- `make test` - Run all tests
|
||||
- `make list-issues` - Show all Gitea issues with status
|
||||
- `make list-issues` - Show all Forgejo issues with status
|
||||
- `make show-issue NUM=X` - Show detailed view of specific issue
|
||||
|
||||
### Workspace Management Understanding
|
||||
|
|
@ -306,7 +306,7 @@ Extend data access layer with search methods. Consider adding full-text search f
|
|||
- **Issue Tracker Integration:** Compatible with Gitea, GitHub, and similar platforms
|
||||
- **Issue Reading:** Use `IssueFetcher` for programmatic access
|
||||
- **Issue Writing:** Use `IssueWriter` for updates via authenticated PATCH
|
||||
- **Environment Variables:** `GITEA_API_TOKEN` or platform-specific tokens for authentication
|
||||
- **Environment Variables:** `FORGEJO_API_TOKEN` or platform-specific tokens for authentication
|
||||
|
||||
### Test Framework
|
||||
- **pytest-based:** All tests use pytest framework
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ Remove tests when:
|
|||
- Update tests to reflect new command structures and access patterns
|
||||
|
||||
### Backend Systems
|
||||
- **Primary**: Gitea backend for issue management
|
||||
- **Primary**: Forgejo backend for issue management
|
||||
- **Secondary**: Local plugin for offline/alternative workflows
|
||||
- **Focus**: Prioritize tests for actively used functionality
|
||||
|
||||
|
|
@ -122,7 +122,7 @@ ACTION: Modify assertions to match new CLI structure
|
|||
### Scenario 2: Obsolete Functionality
|
||||
```
|
||||
FAILING: test_local_plugin_sequential_numbering()
|
||||
CAUSE: Local plugin not actively used, Gitea is primary backend
|
||||
CAUSE: Local plugin not actively used, Forgejo is primary backend
|
||||
DECISION: Remove test as functionality is not essential to current workflow
|
||||
ACTION: Remove test method and document rationale
|
||||
```
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue