-
Hi,
First, thanks for this usefull plugin.
But I have a small issue.
I configured Jenkins with git plugin to build several branches pattern :
- `gitlab/story/*`
- `gitlab/bug/*`
- `gitlab/dev`
(`g…
-
Our current git flow configuration:
```
[gitflow "branch"]
master = master
develop = development
[gitflow "prefix"]
feature = feature/
release = release/
hotfix = hotfix/
support = suppor…
-
Dear sir, I'm new to git, and I saw these instructions on your blog:
- Fork the project.
- Clone your fork into a local repository.
- Switch to the dev (development) branch.
- Branching out from the d…
-
Use gitflow as a branching model.
-
Hi there guys!
@caferrari suggested we use this branching model http://nvie.com/posts/a-successful-git-branching-model/
There's also a command line tool to help that from the same author: https://gi…
-
We need to clearly specify what is the workflow that everybody should follow when submitting patches to the master branch. In short:
- git pull
- git branch -b master issue
- commit many times
- git r…
-
[ERROR] Failed to execute goal on project autodoc: Could not resolve dependencies for project com.theoryinpractise.it:autodoc:clojure:testing: Could not find artifact org.clojure:clojure-contrib:jar:1…
-
I proposed dropping the "flow" command for start/finish tasks and using optional arguments and defaults instead of feature/release/hotfix/support.
Instead of
```
git flow start [type]
git flow finis…
-
extend current script with possibility to toggle the skype/pidgin roster. current action of opening a chat will become `pyimc new-chat`, roster toggle `pyimc toggle`, if only one im app is being used …