(→Search: add explanation) |
(Add section about rewriting history) |
||
| Line 307: | Line 307: | ||
The answer is credential helper | The answer is credential helper | ||
{{References}} | <br /> | ||
== Rewriting History == | |||
Developers need git as a way to track changes and collaborate on software. Release Engineers need git, and '''higher-level''' tools to manage entire repositories of code. Whether Developer or Release Engineer, sometimes you need a do over. | |||
When [https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History rewriting history in your git project], If an interactive git rebase using 'edit' or 'reword' doesn't suffice for your use-case, you are probably looking for a higher-level tool. | |||
To make subtle changes, or even large changes on a whole series of commits in a git repository, [https://github.com/newren/git-filter-repo/ <code>git filter-repo</code>](Python) is that tool. The git maintainers themselves do '''NOT''' recommend using <code>git filter-branch</code> - which is slow and painful and prone to problems. Consult the '''Git Filter Repo''' [https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html User Manual] for examples.{{References}} | |||
[[Category:Development]] | [[Category:Development]] | ||
[[Category:Version Control]] | [[Category:Version Control]] | ||
edits
