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 @ 5c8c290a
...@@ -36,6 +36,22 @@ This guide takes you step-by-step through our Gitlab workflow from issue to comp ...@@ -36,6 +36,22 @@ This guide takes you step-by-step through our Gitlab workflow from issue to comp
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.
6. Begin development 6. Begin development
##### PhpStorm Gitflow Workflow
This assumes that you have already installed the [PhpStorm Gitflow](phpstorm-git-flow) plugin. All interaction with Gitflow is done via the **Gitflow** menu towards the right-side of the PhpStorm **Status Bar**, which is located at the bottom of the screen. If you do not see your status bar, make sure to enable the **View** > **Status Bar** option in your PhpStorm menu.
1. If the Gitflow menu says *"No Gitflow"*, install Gitflow for the project
1. Make sure your working directory is clean *(you don't have any files that are being tracked and have been modified, but not committed)*.
2. From the Gitflow menu, choose **Init Repo**
3. Click the **OK** button accepting the default settings
* Gitflow has created a **develop** branch for you, and checked it out
2. Choose either **Start Feature**, **Start Release** or **Start Hotfix** from the Gitflow menu.
* The type of branch you want to start should be consistent with type of issue you are trying to complete. If the Gitlab issue has a label of `bug`, then you would choose **Start Hotfix**, if the Gitlab issue has a label of `enhancement`, then you would choose **Start Feature** and so on.
3. Name the new branch (Gitflow will prepend either `feature/`, `release/` or `hotfix/` to the branch name for you)
* The name should be a lowercased, dash-separated and a potentially shorter version of the Gitlab Issue **Subject** - e.g. `restrict-droppable-for-draggables`
4. Gitflow created the branch (based on your **develop** branch), and checked it out
5. If you would like to create the branch on Gitlab (for collaborative purposes), you can choose **Publish Feature** from the Gitflow menu.
##### PhpStorm Workflow ##### PhpStorm Workflow
There are several ways to access the Git commands in PhpStorm. These instructions make use of the **Navigation Bar** at the top of the PhpStorm window and the **Status Bar** at the very bottom of the PhpStorm window. Make sure they are visible by enabling the **View** > **Navigation Bar** and **View** > **Status Bar** menu items. There are several ways to access the Git commands in PhpStorm. These instructions make use of the **Navigation Bar** at the top of the PhpStorm window and the **Status Bar** at the very bottom of the PhpStorm window. Make sure they are visible by enabling the **View** > **Navigation Bar** and **View** > **Status Bar** menu items.
......
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