Hacker News Reader

Comment by trumbitta2 | Hacker News Reader

The "Create merge request" (from issue) button.

It creates a new branch, with a smart name like 123-my-issue-title, and a new "pull request" for that issue and branch.

A neat hidden feature (AFAIK, maybe it's buried in documentation) is that if you branch locally and name it [issue number]-branch-name, pushing that branch and opening an MR from it will automatically tie it to [issue number] for the same workflow.

Handy for those situations where you started writing code before opening an MR.

I love that you highlighted this! This is basically a mandatory part of the data team's workflow. Once the MR is open we then spin up a clone of our data warehouse tied to that git branch where all the CI jobs run. I like that it will automatically close the issue too once the MR is merged.

Agree. This is indeed a nice tidy workflow. I usually just create a bunch of issues to have a visual representation of what is missing in a project, sort them in a board and then work through them.

Issues are good place for asking input and feedback, and also help in keeping feature branches focused and short lived. Definitely my favorite git workflow.

This sounds similar to Atlassian’s Jira/Bitbucket integration without the jira.

GitLab's value prop can be more or less summed up as 'everyone else gives you ala carte tools, we give you one that's unified'.

Reply on news.ycombinator.com