Timeline for Best Git workflow suitable for our needs
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2014 at 7:45 | comment | added | Esben Skov Pedersen | I dont think you can expect to just cherry pick features to deploy except for very simple things. If a feature dont pass testing you just add more commits to dev until it is fixed. | |
| Sep 23, 2014 at 23:36 | comment | added | Gaui | I'm trying out tagging a feature when it's ready for testing/staging. Gonna see how that works out. | |
| Sep 23, 2014 at 21:05 | comment | added | Gaui | Some features don't pass through testing/staging | |
| Sep 23, 2014 at 20:01 | comment | added | Esben Skov Pedersen | Reverting? Why are you reverting? | |
| Sep 23, 2014 at 18:13 | comment | added | Gaui | I just tried this out today and it went horribly. Cheery picking the features from dev to staging and master went well. But when it came to reverting and merge'ing master into staging and dev, it began to conflict. We have to find another strategy where we'll merge. | |
| Sep 22, 2014 at 11:19 | history | edited | Esben Skov Pedersen | CC BY-SA 3.0 | added advanced branching strategy |
| Sep 20, 2014 at 19:24 | history | answered | Esben Skov Pedersen | CC BY-SA 3.0 |