Timeline for Git branches avoided by the office where I work
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4, 2014 at 4:34 | comment | added | Móż | One benefit from merging is that you find places where a bug was only fixed in one branch, which can be hugely beneficial if both branches have been released. Where I work we have no "common" repository, just multiple copies of some files. Merging those fixed a number of significant issues. | |
| Jul 4, 2014 at 4:33 | comment | added | Móż | should we autoformat reduces some of the hassle with merging. There is a code formatting standard, it's mechanically applied, therefore two copies of the same code must have identical format. | |
| Jul 4, 2014 at 1:48 | history | answered | mattnz | CC BY-SA 3.0 |