-
Notifications
You must be signed in to change notification settings - Fork 3
feat: standardize app to opensource it #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
44e5c75 to
8379568
Compare
Add comprehensive specification for preparing the repository for open-source release under Apache 2.0 license. Includes task breakdown covering: - Apache 2.0 licensing artifacts (LICENSE, README updates) - README refresh with visual asset and improved structure - Contribution guidelines (CONTRIBUTING.md) - GitHub issue templates (bug, feature, question) - Semantic versioning and release documentation Also update pre-commit config to exclude MD041 (first line heading) rule to accommodate spec document format. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Add Apache 2.0 license to repository with complete supporting documentation: - Add LICENSE file with official Apache 2.0 text - Add license badge to README - Add License section with file reference in README - Update pyproject.toml with license field - Exclude LICENSE from markdownlint checks - Update task tracking (tasks 1.1-1.3 complete) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- embed a header graphic to give the README a visual entry point - add a mermaid sequence diagram that explains the SDD workflow - reference CONTRIBUTING.md alongside the operations guide for contributors
- Adds CONTRIBUTING.md with setup, testing, commits, PRs, CoC placeholder - References docs/operations.md and issue templates - Runs tests and pre-commit hooks - Updates task list: marks 3.1–3.5 and 3.0 complete Related to tasks 0002
- Add bug, feature, and question forms using Issue Forms schema - Add config to disable blank issues and link to docs - Add title prefixes and default labels for triage - Validate with pre-commit (check-yaml, markdownlint) - Update 0002/4.0–4.5 tasks as completed
- add uv-based CI jobs for tests, linting, coverage, and commitlint - configure semantic release with octo-sts identity and uv lock refresh - align developer tooling via pre-commit defaults, coverage ignores, and pyproject metadata - add placeholder pytest
8379568 to
f6c2a71
Compare
03f4616 to
91371ad
Compare
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
WalkthroughAdds open-source readiness assets: Apache-2.0 license, CONTRIBUTING, README updates, GitHub issue/PR templates and config, CI (tests/lint/coverage) and release workflows with STS, pre-commit configuration, gitignore updates, pyproject/tooling changes, task docs, and a placeholder test. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor Dev as Developer
participant GH as GitHub
participant CI as CI Workflow (ci.yml)
participant Test as Pytest
participant Lint as Ruff/Pre-commit
participant Cov as Codecov
Dev->>GH: Push / Open PR
GH-->>CI: Trigger CI workflow
CI->>CI: Setup Python 3.12 + uv, sync deps
CI->>Test: Run pytest (collect coverage)
Test-->>CI: coverage.xml + results
CI->>Cov: Upload coverage
CI->>Lint: Run ruff + pre-commit checks
Lint-->>CI: lint results
CI-->>GH: Report job statuses
sequenceDiagram
autonumber
participant GH as GitHub
participant Release as Release Workflow (release.yml)
participant STS as octo-sts/action
participant SR as python-semantic-release
GH-->>Release: workflow_run (success)
Release->>STS: Request scoped OIDC token
STS-->>Release: Provide GITHUB_TOKEN-equivalent
Release->>Release: Checkout full history, configure git
Release->>SR: Run semantic-release publish
SR-->>GH: Create tag/release and update changelog
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 4
🧹 Nitpick comments (1)
.github/ISSUE_TEMPLATE/config.yml (1)
3-4: Fix the contact link repositoryThe documentation link goes to
liatrio/spec-driven-development-mcp, which is a different repo. Contributors following it will hit the wrong project. Please point this link at the README for this repository instead.Apply this diff:
- - name: Documentation - url: https://github.com/liatrio/spec-driven-development-mcp#readme + - name: Documentation + url: https://github.com/liatrio-labs/spec-driven-workflow-mcp#readme
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (2)
misc/header.pngis excluded by!**/*.pnguv.lockis excluded by!**/*.lock
📒 Files selected for processing (17)
.github/ISSUE_TEMPLATE/bug_report.yml(1 hunks).github/ISSUE_TEMPLATE/config.yml(1 hunks).github/ISSUE_TEMPLATE/feature_request.yml(1 hunks).github/ISSUE_TEMPLATE/question.yml(1 hunks).github/chainguard/main-semantic-release.sts.yaml(1 hunks).github/pull_request_template.md(1 hunks).github/workflows/ci.yml(1 hunks).github/workflows/release.yml(1 hunks).gitignore(1 hunks).pre-commit-config.yaml(1 hunks)CONTRIBUTING.md(1 hunks)LICENSE(1 hunks)README.md(4 hunks)pyproject.toml(1 hunks)tasks/0002-spec-open-source-ready.md(1 hunks)tasks/tasks-0002-spec-open-source-ready.md(1 hunks)tests/test_placeholder.py(1 hunks)
🔇 Additional comments (1)
.github/workflows/ci.yml (1)
51-57: Verify Codecov token/app setup.
codecov/codecov-action@v4will no-op without either aCODECOV_TOKENsecret or the Codecov GitHub App installed on this repo. That would silently drop coverage reports (the step prints a warning but still passes becausefail_ci_if_erroris false). Please confirm the integration/token is configured, or add it before merging.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
.github/chainguard/main-semantic-release.sts.yaml(1 hunks)CONTRIBUTING.md(1 hunks)README.md(4 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
- .github/chainguard/main-semantic-release.sts.yaml
- CONTRIBUTING.md
iaminawe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me @ryderstorm - all the essential elements for open sourcing are in place and this looks like a good template for future open source projects.
Why?
Establish the repository as an open-source ready project with clear licensing, contribution guidance, and quality automation so external collaborators can confidently adopt the spec-driven development workflow.
What Changed?
LICENSEfile and surfaced the license badge/section in README.md..github/ISSUE_TEMPLATE/for bugs, feature requests, and questions, plus enforcing configuration.Run tests and linting) and release pipelines under.github/workflows/, along with Chainguard semantic-release settings..pre-commit-config.yaml, updated pyproject.toml anduv.lockwithpytest,ruff, and editable project metadata, and added placeholder tests intests/test_placeholder.py.tasks/0002-spec-open-source-ready.mdand tasks/tasks-0002-spec-open-source-ready.md.misc/header.pngused by the refreshed README hero section.Summary by CodeRabbit
Documentation
Chores
Tests