public marks

PUBLIC MARKS with tags gitlab & git

This year

Danger - Stop Saying "You Forgot To…" in Code Review

by Spone
Danger runs during your CI process, and gives teams the chance to automate common code review chores. This provides another logical step in your build, through this Danger can help lint your rote tasks in daily code review. You can use Danger to codify your teams norms. Leaving humans to think about harder problems. She does this by leaving messages inside your PRs based on rules that you create with the Ruby scripting language. Over time, as rules are adhered to, the message is amended to reflect the current state of the code review.

2016

2015

Howto: One time migration from SVN to GitLab with non-standard SVN layout | Igor's Blog

by srcmax
I've finally got around to moving the SVN repository that supports all the source code for this blog to Git, specifically GitLab. There were a few hurdles and I came across and many existing articles were useful but didn't quite address my specific case.

GitLab Flow | GitLab

by Spone & 1 other
Version management with git makes branching and merging much easier than older versioning systems such as SVN. This allows a wide variety of branching strategies and workflows. Almost all of these are an improvement over the methods used before git. But many organizations end up with a workflow that is not clearly defined, overly complex or not integrated with issue tracking systems. Therefore we propose the GitLab flow as clearly defined set of best practices. It combines feature driven development and feature branches with issue tracking.

GitLab Flow | GitLab

by srcmax & 1 other
Version management with git makes branching and merging much easier than older versioning systems such as SVN. This allows a wide variety of branching strategies and workflows. Almost all of these are an improvement over the methods used before git. But many organizations end up with a workflow that is not clearly defined, overly complex or not integrated with issue tracking systems. Therefore we propose the GitLab flow as clearly defined set of best practices. It combines feature driven development and feature branches with issue tracking.

Active users

mfaure
last mark : 09/11/2017 17:05

NiMe
last mark : 12/04/2017 13:03

Spone
last mark : 18/01/2017 21:23

srcmax
last mark : 28/10/2015 12:07