Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D digitec-wiki
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Digitec
  • digitec-wiki
  • Wiki
  • gitlab issues workflow

gitlab issues workflow · Changes

Page history
rcabral created page: phpstorm-git-flow authored Feb 17, 2014 by Mike McLin's avatar Mike McLin
Show whitespace changes
Inline Side-by-side
gitlab-issues-workflow.markdown
View page @ 538abff2
...@@ -30,7 +30,7 @@ This guide takes you step-by-step through our Gitlab workflow from issue to comp ...@@ -30,7 +30,7 @@ This guide takes you step-by-step through our Gitlab workflow from issue to comp
1. Checkout **master** branch 1. Checkout **master** branch
2. Pull changes from **origin/master** 2. Pull changes from **origin/master**
3. Create a new issue/development branch from **master** following these naming conventions... 3. Create a new issue/development branch from **master** following these naming conventions...
* Should start with a (single) main **label** for the Gitlab Issue, followed by a slash - e.g. `bug/` * Should start with either `feature/`, `release/` or `hotfix/`
* Should be a lowercased, dash-separated and a potentially shorter version of the Gitlab Issue **Subject** - e.g. `bug/restrict-droppable-for-draggables` * Should be a lowercased, dash-separated and a potentially shorter version of the Gitlab Issue **Subject** - e.g. `bug/restrict-droppable-for-draggables`
4. Checkout the new issue/development branch 4. Checkout the new issue/development branch
5. Create remote branch by pushing to origin using the same branch name. 5. Create remote branch by pushing to origin using the same branch name.
......
Clone repository
  • alpha beta testing
  • browser testing
  • camtasia licenses
  • code delivery processes
  • coding practices
  • css and sass coding standards
  • database schema standards
  • dependency management
  • development environments
  • digitec agile process
  • digitec gitlab styles
  • digitec software promises
  • digitec spec process
  • gitlab administration
  • gitlab issues tags
View All Pages