Skip to content

Latest commit

 

History

History
41 lines (27 loc) · 1.44 KB

COCOGITTO_FIX_SUMMARY.md

File metadata and controls

41 lines (27 loc) · 1.44 KB

Cocogitto Configuration Fix Summary

Changes Made

This PR configures cocogitto to validate commits from the latest release tag (v0.1.0) forward by setting:

from_latest_tag = true

This is the recommended approach for projects with existing non-compliant commits in their history.

Current Status

✅ Configuration updated in cog.toml
⚠️ 3 "Initial plan" commits remain after v0.1.0 tag that don't follow conventional commits format

Why These Commits Still Fail

The 3 "Initial plan" commits (8c61d60, 25cc1e3, 2dd039f) were created after the v0.1.0 tag was applied, so they are within the validation scope even with from_latest_tag = true.

Solution Options

Option 1: Rewrite history (Recommended for full fix)

git rebase -i v0.1.0
# Change "Initial plan" to "chore: initial plan"
git push --force-with-lease

Option 2: Create new tag after these commits

If these commits are acceptable as-is, create a new release tag (e.g., v0.1.1) after them, then cocogitto will only validate commits after that new tag.

Option 3: Accept current state

Keep the current configuration. Future commits will be validated, but these 3 historical commits will continue to fail cog check.

Impact

  • ✅ Configuration prevents validation of very old non-compliant commits
  • ⚠️ Release workflow may still fail due to the 3 remaining non-compliant commits
  • ✅ All future commits must follow conventional commits format