-
We should write tests for the extension.
-
Although gh-pages branches aren't really part of the original Gitflow model, they are a special type of branch that we end up dealing with when working with GitHub.
Hubflow needs to support the gh-pa…
-
A few years back we adopted the [Gitflow branching model](https://nvie.com/posts/a-successful-git-branching-model/), and since then we've discussed and added further rules to our branching model such …
-
### Summary
The Duality repo currently uses a custom setup for its branches and workflow. To make it easier for new contributors to understand the process, consider adopting the widely used [git fl…
ilexp updated
4 years ago
-
See #502 for some context.
The old pattern of having someone work on a branch for months or years before merging wholesale is becoming difficult to manage. More specifically:
* the task of revie…
-
**Is your feature request related to a problem? Please describe.**
Apparently the current development model is more "trunk" based than what Git was designed for. As such I myself have made mistakes e…
-
Once truly approaching a first public version, create a release candidate `1.0-rc1` using the git-flow mechanisms.
Could also create beta versions, but that seems like overdoing it...
This shall a…
-
As architect, I would like to revise the branching strategy so that it makes more sense to everyone.
---
At present when the main branch is updated on a repository, it automatically generates a rele…
-
Expanding git-flow is becoming increasingly tedious. The subcommand structure isn't flexible enough to support heterogenous subcommand styles and flag parsing is a pain in the ass to get right on all …
nvie updated
11 years ago
-
The current "trunk-based" development for fragalysis (stack, backend, frontend) makes delivering features and milestone safely very difficult.
If we follow a modified "[gitflow](https://www.atlassi…