Skip to content

[Discussion] Branch name guidelines #43

Description

@cguedes

Should we have rules for branch names?

For now I've seen we using:

A) username/something
B) feature-something
C) issuenumber-description-extra (based on GitHub UI Create a branch for this issue)

I link the option C as it's easy to read the issue number and also the feature scope. Also can be automatically generated if we start the new feature workflow from the GitHub issue page.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions