Clarify terminology: from "convention" to "documented workflow"

[warengonzaga]

Problem

During a recent discussion about the Clean Commit project, a community member pointed out that the term convention usually implies broader adoption, whereas my project currently reflects a personal workflow I’ve documented and shared.

I originally described it as a "convention" because it’s a standardized practice I’ve followed for years across my projects. However, I recognize that adoption is what truly makes something a convention. Based on this feedback, I’ll adjust the wording in the repo to emphasize that this is a documented workflow/personal standard.

• Update README and documentation to replace the term convention with documented workflow or personal standard.
• Add a note that if others adopt it, it can evolve into a convention over time.
• Ensure messaging highlights transparency: the workflow is mine, refined with AI assistance for documentation, but rooted in years of practice.

Outcome

This change will make the project description more accurate, reduce confusion, and show responsiveness to community feedback.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

_{You can configure auto-planning by selecting labels in the issue_enrichment configuration.}

🔗 Similar Issues

Related Issues

• https://github.com/wgtechlabs/package-build-flow-action/issues/4
• Rename latest flow to staging for better CI/CD semantics container-build-flow-action#5
• Enhance README: Add 'Who Uses Clean Commit?' Section #3

👤 Suggested Assignees

• warengonzaga

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!