Contributors mailing list archives

Browse archives


Re: pre-commit changes

Tecnativa. S. L., Pedro M. Baeza
- 05/12/2022 08:28:06
The idea of the first pre-commit set is to store the automatic changes, so you don't have to review them extensively. The rest of the manual changes to make the linter happy must be on the migration commit, as a third extra commit doesn't make too much sense. You have to review these manual changes, and they can be even provoked by the new code you are introducing for the migration, so better to have all of them in the same migration commit.