|
|
|
|
|
|
by heavenlyblue
2703 days ago
|
|
|
What if my repository is linked to a CI process that deploys the live code? And tb change needs to be done “now”? If you are working for a larger company where processes are clearly defined, then it’s good for you and that feature is not needed. But you are loosing all of the agile feature of git in the first place. In my situation squashing history takes away my other ability to use git as a wiki of “things that didn’t work out”. It’s important to keep that. |
|
|
Wouldn't a wiki be the best solution for that? Git is a software development tool, not a design or project management tool.