You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: add workflow comparison section to README #80
README targets Claude Code users specifically but doesn't explain how this Gitflow skill compares to other common git workflows. Users coming from trunk-based development, GitHub Flow, or squash-merge strategies may not understand the value proposition or trade-offs.
Expected behavior
Add a brief comparison section to README (or a separate COMPARISON.md linked from README) covering:
Gitflow vs GitHub Flow — when to use which, trade-offs
Conventional Commits vs free-form — why structured messages matter
Merge commits vs squash — why this skill enforces --no-ff merge commits
Issue-driven vs ad-hoc branching — traceability benefits
Keep it concise — a table or short paragraphs, not an essay. The goal is to help users make an informed decision about adopting this workflow.
Activity
Merge pull request #84 from qubernetic-org/docs/80-workflow-comparison
github-actions commentedon Mar 27, 2026
Closed by #84 (merged into
develop).