Timeline for Solution with multiple projects and (GitHub) single issue tracker and repository
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 31, 2013 at 13:49 | comment | added | DaveWeber | There's scenarios where it could become a lot messier than just reverting a single commit, and rewriting history can be very dangerous. For instance, what if a faulty piece of code propagates through multiple commits, or a large amount of work is dependent on such a feature? Speaking from personal experience there, but maybe it's an edge case. | |
| Oct 31, 2013 at 7:44 | comment | added | iveqy | Either you do a git revert to remove a single commit or you rewrite history. If instead of doing a git reset (as I think you mean with rollback) you do a git rebase -i and just remove the faulty commit. You've solved the problem of wiping out changes to other parts of the project. You're fine as long as you don't have unrelated changes in the same commit. | |
| Oct 31, 2013 at 4:38 | history | answered | DaveWeber | CC BY-SA 3.0 |