← Back to context Comment by QuercusMax 2 months ago Your hook really shouldn't be running on the merge commit unless you have conflicts in your merge. 3 comments QuercusMax Reply mcv 2 months ago Never had conflicts on a merge? We've got a lot of people on the same codebase. Merge conflicts are a fact of life. And they wouldn't be a problem without the stupid commit hook. It's the commit hook that makes them a problem. QuercusMax 2 months ago If you have conflicts then you can fix them and run your linter or formatter. If you have a no conflict merge it doesn't matter. mcv 2 months ago Thanks, but that's not the issue here.
mcv 2 months ago Never had conflicts on a merge? We've got a lot of people on the same codebase. Merge conflicts are a fact of life. And they wouldn't be a problem without the stupid commit hook. It's the commit hook that makes them a problem. QuercusMax 2 months ago If you have conflicts then you can fix them and run your linter or formatter. If you have a no conflict merge it doesn't matter. mcv 2 months ago Thanks, but that's not the issue here.
QuercusMax 2 months ago If you have conflicts then you can fix them and run your linter or formatter. If you have a no conflict merge it doesn't matter. mcv 2 months ago Thanks, but that's not the issue here.
Never had conflicts on a merge? We've got a lot of people on the same codebase. Merge conflicts are a fact of life. And they wouldn't be a problem without the stupid commit hook. It's the commit hook that makes them a problem.
If you have conflicts then you can fix them and run your linter or formatter. If you have a no conflict merge it doesn't matter.
Thanks, but that's not the issue here.