Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.editor beat.editor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.editorbeat.editor
  • Issues
  • #192
Closed
Open
Issue created Jan 19, 2019 by Jaden DIEFENBAUGH@jdiefenbaughContributor

[meta] Naming branches to associate it with an issue

In doc/contribute.rst, we say that "branches should have meaningful names". We give two examples, one of which actually references the issue number. Could we require that all branches directly reference the issue the branch is addressing? So names like the following are fine:

  • "issue_20_fix_wrong_index"
  • "implement_db_editor_248"

But names like the following aren't okay except in rare cases:

  • "fix_wrong_index"
  • "implement_db_editor"

I personally find it hard to understand what someone is doing in a branch when they don't reference an existing issue.

[edit]:

Final decision: <issue_number>_name_of_the_branch

Edited Feb 25, 2019 by Samuel GAIST
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking