Skip to content

updadted project standards#26

Merged
Mjoyufull merged 2 commits intodevfrom
docs/project_standards
Feb 23, 2026
Merged

updadted project standards#26
Mjoyufull merged 2 commits intodevfrom
docs/project_standards

Conversation

@Mjoyufull
Copy link
Owner

@Mjoyufull Mjoyufull commented Feb 23, 2026 •
edited by cubic-dev-ai bot
Loading

updated readme

Summary by cubic

Updated PROJECT_STANDARDS.md to tighten release and hotfix rules and bump the doc to v1.3.0. Main is only updated via release or hotfix branches; adds strict tagging and an expanded release body template.

  • Documentation
    • main and dev never merge directly; only after a hotfix or a docs-only change to main.
    • Release branches are for version bumps and docs only (no code). Merge to main, then back to dev; delete only after both merges. Naming: release/3.0.0-.
    • Hotfixes branch from main; contributor submits code-only, maintainer bumps version, tags and publishes, then merges main into dev. Reverts are handled as hotfixes.
    • Tag = version number only (no codename or “v” unless project convention); GitHub release title is [version-codename]. Added a structured release body template with required sections and rules.
    • Added guidance for syncing main into dev after hotfix/docs-only changes, including conflict resolution priorities (prefer the hotfix side for code).

Written for commit 660d01d. Summary will update on new commits.

@Mjoyufull Mjoyufull changed the base branch from main to dev February 23, 2026 05:50
cubic-dev-ai[bot]
cubic-dev-ai bot reviewed Feb 23, 2026
View reviewed changes
Copy link

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Prompt for AI agents (all issues) 

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="PROJECT_STANDARDS.md">

<violation number="1" location="PROJECT_STANDARDS.md:683">
P2: Inconsistent release branch naming: this section uses `release/3.0.0-kiwicrab` (no `v` prefix), but the "Release Management → Preparation" and "Process" sections still use `release/v3.0.0-kiwicrab`. The two example code blocks in the same document disagree on whether release branch names include a `v` prefix. Consider aligning them (likely dropping the `v` everywhere, to match the updated Git tag convention).</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

Mjoyufull
Mjoyufull commented Feb 23, 2026
View reviewed changes
Copy link
Owner Author

@Mjoyufull Mjoyufull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Mjoyufull Mjoyufull merged commit ee24591 into dev Feb 23, 2026
1 of 5 checks passed
@Mjoyufull Mjoyufull deleted the docs/project_standards branch February 23, 2026 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cubic-dev-ai cubic-dev-ai[bot] cubic-dev-ai[bot] left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Mjoyufull