-
Basically, we have two main branches: master and develop branch.
The development should be push to the develop branch. After all functions became stable, we can merge into the master branch.
- h…
mssun updated
7 years ago
-
After discussion with @phanimahesh concerning our CI flows, we might want to rethink our branching strategy to align both development and CI.
@phanimahesh suggested workflow:
http://nvie.com/posts/a…
-
**3.3.1**
**Windows 7 Pro 64 bit**
**Folger FT5**
** I used the same part and settings in Cura 3.3.1 and Cura 3.2.1**
**According to Cura 3.3.1 the print will take an hour long…
-
So this has been on my mind for a few months now, and frustratingly I can't find the link but I recall Taylor saying a few months back there would be no breaking changes in each update to Laravel 5.5 …
-
I was wondering if it would be possible to adjust the branching strategy used for development of Mastodon. In the current state master is a pool of chaos and not a trusted source for a stable producti…
-
Should we adapta Gitflow workflow here as well?
For me it would make sense, since the site is getting bigger and as with the unintended merge in #43, we can establish a fallback for the main site.
…
-
If you have questions or bugs with git branches just use this chat
docs: https://git-scm.com/docs/git-branch
CIA tutorial: https://wikileaks.org/ciav7p1/cms/space_1736707.html
a popular model of…
-
Consider start using the GitFlow workflow for versioning?
Here's a few things it would solve:
- It would keep master at a release version, meaning people could actually install from git with npm…
-
I propose all contributors to follow some Git workflow similar to [Gitflow workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow). It will allow to keep `master` branc…
-
For consideration, proposing to adopt the GitFlow branching/workflow scheme as detailed here:
http://nvie.com/posts/a-successful-git-branching-model/
This would require us to ideally merge all e…