-
-
Per the [GitFlow documentation](http://datasift.github.io/gitflow/IntroducingGitFlow.html) we should use a `develop` branch for our development code.
- Create a develop branch
- Document the inten…
-
- [centralized-workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/centralized-workflow)
- [feature-branch-workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/feat…
-
Hi!
I have been thinking a lot about the naming convention for existing branches and I think that we should rename branch 2.2.0 to master once for all and have the master to be the one where all de…
-
hi
I was wondering what is the git workflow when creating libraries ?
If I have a library that uses angular 4.x and the same library that uses angular 5.x
should they be in the same repo in …
-
On a certain branch in a local repo I was working on, `gitversion` command returns `MajoMinorPatch=0.1.0`. However, when I make a fresh clone of the same repo, `gitversion` produces `2.1.0`.
Both n…
-
- [x] Rename `test` occurrences to `example`, as they are not technically tests.
- [x] Update figure.
-
Hello,
would it be possible to provide anywhere some sort of list of features when a new release come up?
I've seen the new `5.0` and wondering what is new there.
Thank you a lot for your great w…
-
In my opinion, when we merge PRs, we should be squashing the commits before merging it. A PR is usually related to one logical change as:
- during the course of development, developers usually keep …
-
Given that we're actually releasing to PyPI, I think it makes sense to use a gitflow workflow (see [here](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) and [here](http:…
jsf9k updated
7 years ago