4 ms·
One of the easiest tools in this regard is just a “test” that blocks merging if the request is n commits behind master—just enforcing a rebase whenever you upda
by crdrost 3y ago
One of the easiest tools in this regard is just a “test” that blocks merging if the request is n commits behind master—just enforcing a rebase whenever you update a pull request. Combine with forbidding fast forward merges for pull requests (just let the code review tool generate a merge commit) and your `git log --graph` becomes much mor bounded in terms of how bad it can get.
- eru 3y agoDo you see `git log --graph` becoming entangled as a problem in itself, or as a symptom of a problem? Your suggestion seems to help with the former, but not really the latter, or does it? You might like https://bors.tech/ https://bors.tech/ however.