Compare commits

...

2 commits

Author SHA1 Message Date
de368271f6 docs: finish Forgejo product language in Makefile help
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Keep publish-gitea / issue-backend-set-gitea as target names; help
text now names Forgejo as the product.

Assistant: grok
Assistant-Session: 01a09dc6-3f0d-7c93-8b11-8e83c0623d49
2026-09-14 04:54:50 +02:00
360bd29540 chore: refresh WORK-RECORDS.md after ISSUE-WP-0006 close
Index now shows ISSUE-WP-0006 and T01–T04 as finished/done.

Assistant: grok
Assistant-Session: 01a09dc6-3f0d-7c93-8b11-8e83c0623d49
2026-09-14 04:54:20 +02:00
3 changed files with 13 additions and 13 deletions

View file

@ -39,7 +39,7 @@ help: ## Show issue core capability help
@echo " test-verbose Run tests with verbose output"
@echo " package Build source and wheel distributions"
@echo " package-check Build and validate distributions"
@echo " publish-gitea Publish distributions to Gitea PyPI"
@echo " publish-gitea Legacy alias: publish to old Gitea PyPI URL (prefer publish-forgejo)"
@echo ""
@echo "Feedback & Continuous Improvement:"
@echo " feedback MSG=\"...\" Submit feedback about issue-core"
@ -148,7 +148,7 @@ endif
issue backend set local
.PHONY: issue-backend-set-gitea
issue-backend-set-gitea: ## Configure Gitea backend (requires REPO=repository-name)
issue-backend-set-gitea: ## Configure Forgejo backend (type string gitea; requires REPO=repository-name)
ifndef ISSUE_CLI
@echo "❌ Issue facade not installed"
@exit 1
@ -230,7 +230,7 @@ package-check: package ## Build and validate source/wheel distributions
$(PYTHON) -m twine check dist/*
.PHONY: publish-gitea
publish-gitea: package-check ## Publish distributions to the Coulomb Gitea PyPI registry
publish-gitea: package-check ## Legacy: publish to the old Coulomb Gitea PyPI URL (prefer publish-forgejo)
ifndef TWINE_USERNAME
$(error TWINE_USERNAME is required)
endif
@ -320,7 +320,7 @@ issue-core-demo: ## Demonstrate facade functionality
@echo "The Issue Core provides a unified CLI for issue tracking across:"
@echo " • GitHub Issues"
@echo " • GitLab Issues"
@echo " • Gitea Issues"
@echo " • Forgejo Issues"
@echo " • Local SQLite storage"
@echo ""
@echo "Key features:"
@ -350,8 +350,8 @@ issue-detect-repo: ## Detect and configure backend for current repository
echo "🐙 GitHub remote detected"; \
elif git remote -v 2>/dev/null | grep -q gitlab; then \
echo "🦊 GitLab remote detected"; \
elif git remote -v 2>/dev/null | grep -q gitea; then \
echo "🦋 Gitea remote detected"; \
elif git remote -v 2>/dev/null | grep -qE 'forgejo|gitea'; then \
echo "🦋 Forgejo remote detected"; \
else \
echo "📁 Generic git repository - local backend recommended"; \
fi; \
@ -395,7 +395,7 @@ capability-info: ## Show capability information
@echo "Description: $(CAPABILITY_DESCRIPTION)"
@echo "Type: CLI application with backend facade pattern"
@echo "Main command: issue"
@echo "Supported backends: Local SQLite, GitHub, GitLab, Gitea"
@echo "Supported backends: Local SQLite, Forgejo, GitHub, GitLab"
@echo "Key features: Repository-aware, offline-capable, unified interface"
@echo "Targets:"
@$(MAKE) --no-print-directory help | grep "^ " | sed 's/^ / /'

View file

@ -13,7 +13,7 @@
| workplan | ISSUE-WP-0003 | finished | — | workplans/ISSUE-WP-0003-railiance01-deployment.md |
| workplan | ISSUE-WP-0004 | finished | — | workplans/ISSUE-WP-0004-align-with-work-record-canon.md |
| workplan | ISSUE-WP-0005 | finished | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md |
| workplan | ISSUE-WP-0006 | ready | — | workplans/ISSUE-WP-0006-forgejo-only-projection-boundary.md |
| workplan | ISSUE-WP-0006 | finished | — | workplans/ISSUE-WP-0006-forgejo-only-projection-boundary.md |
| workplan | ISSUE-WP-0007 | finished | — | workplans/ISSUE-WP-0007-rapp-issue-core-railiance01-migration.md |
| task | T01 | done | — | workplans/ISSC-WP-0001-rename-and-task-ingestion.md |
| task | T02 | done | — | workplans/ISSC-WP-0001-rename-and-task-ingestion.md |
@ -43,10 +43,10 @@
| task | ISSUE-WP-0005-T07 | done | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md |
| task | ISSUE-WP-0005-T08 | done | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md |
| task | ISSUE-WP-0005-T09 | done | — | workplans/ISSUE-WP-0005-connector-alignment-implementation.md |
| task | ISSUE-WP-0006-T01 | todo | — | workplans/ISSUE-WP-0006-forgejo-only-projection-boundary.md |
| task | ISSUE-WP-0006-T02 | todo | — | workplans/ISSUE-WP-0006-forgejo-only-projection-boundary.md |
| task | ISSUE-WP-0006-T03 | todo | — | workplans/ISSUE-WP-0006-forgejo-only-projection-boundary.md |
| task | ISSUE-WP-0006-T04 | todo | — | workplans/ISSUE-WP-0006-forgejo-only-projection-boundary.md |
| task | ISSUE-WP-0006-T01 | done | — | workplans/ISSUE-WP-0006-forgejo-only-projection-boundary.md |
| task | ISSUE-WP-0006-T02 | done | — | workplans/ISSUE-WP-0006-forgejo-only-projection-boundary.md |
| task | ISSUE-WP-0006-T03 | done | — | workplans/ISSUE-WP-0006-forgejo-only-projection-boundary.md |
| task | ISSUE-WP-0006-T04 | done | — | workplans/ISSUE-WP-0006-forgejo-only-projection-boundary.md |
| task | ISSUE-WP-0007-T00 | done | — | workplans/ISSUE-WP-0007-rapp-issue-core-railiance01-migration.md |
| task | ISSUE-WP-0007-T01 | done | — | workplans/ISSUE-WP-0007-rapp-issue-core-railiance01-migration.md |
| task | ISSUE-WP-0007-T02 | done | — | workplans/ISSUE-WP-0007-rapp-issue-core-railiance01-migration.md |

View file

@ -49,7 +49,7 @@ discovery:
intent: Project and operate on external issue trackers with a stable link to
work-record UUIDs; never replace file-first work records as coordination substrate.
includes:
- unified Python API and CLI over Gitea/SQLite issue operations
- unified Python API and CLI over Forgejo/SQLite issue operations
- work_record_issue_map store + project/map/push-status
- local offline cache and backend sync
- credential handling via environment variables