Timeline for Keeping a clean git history when using gitflow - unmerged commits on develop
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 17, 2019 at 14:48 | vote | accept | Christopher Francisco | ||
| Feb 21, 2017 at 8:08 | answer | added | Sergio Basurco | timeline score: 4 | |
| Dec 28, 2016 at 21:23 | comment | added | Christopher Francisco | @RomanSusi mostly because it's well documented, community is broad so it doesn't feel like "my own [unrefined] approach" and it if it were not by the problem described in my question, I'd be perfect to be honest; At least for property software development (since we need a well structured methodology, rather than just throwing random PRs from time to time) | |
| Dec 28, 2016 at 19:37 | comment | added | Roman Susi | Just 2c: No matter how many devs use it, answer "why?" first for yourself... | |
| Nov 9, 2016 at 23:49 | comment | added | axl | There are several discussions about how to solve various issues with GitFlow on GitHub and other places. Sometimes there just isn't a silver bullet. | |
| Nov 9, 2016 at 2:47 | comment | added | Christopher Francisco | @axl I understand what you mean, but I'm trying to follow gitflow as close as possible to it's documentation. I'd rather not doing any kind of "hackz" because since gitflow is already adopted by many many developers, they should already have a solution for this simple thing | |
| Nov 5, 2016 at 14:30 | comment | added | axl | The merge to master will be a "copy", no need to merge it to develop. Make hot fixes from the previous release branch, not master, and merge to both from there, and you won't have the problem. Master is not adding much to the model so you can actually drop it completely, IMO. | |
| Nov 4, 2016 at 9:28 | comment | added | F.P | Want a clean history? Don't use gitflow. It by definition pollutes your history. Instead, think about what you really need and build a workflow around that, so it actually fits how you want to work. | |
| Nov 3, 2016 at 23:46 | history | tweeted | twitter.com/StackSoftEng/status/794324783177617415 | ||
| Nov 3, 2016 at 21:45 | comment | added | Jace Browning | Please define "clean history". | |
| Nov 3, 2016 at 19:21 | history | asked | Christopher Francisco | CC BY-SA 3.0 |