Skip to content
This repository was archived by the owner on Apr 9, 2026. It is now read-only.
This repository was archived by the owner on Apr 9, 2026. It is now read-only.

Git Workflow changes proposal #53

@radoslavzeman

Description

@radoslavzeman

Suggestions

Some suggestions to change regarding to https://namingconvention.org/git/ and our docs https://bratislava.github.io/onboarding/git-workflow#commit-message-branch-and-pr-name-formats

(Following format is not relevant, only the content)

Branch naming

Must:

  • Include a short descriptive summary in imperative present tense
  • Use Hyphens for separating words
  • Use only small letters
  • Include corresponding issue id if exists (from GitHub issue, Jira, etc.)

Should not:

  • Include the work type: feature, refactor, bugfix, hotfix, feat, fix, etc.
  • Include author's name or initials
  • Use big letters
  • Use slashes or backslashes

Suggested Format:

  • {2-3 word summary}-#{issue id}

Example:

git checkout -b oauth-migration-#244

Commit Message

Should

Should not:

  • Use Conventional Commits

PR Naming

Must:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions