From the position of a contributor, I understand and agree with you. You shouldn't contribute to a project whose terms you do not agree with, and I think that the "CoC" movement helps surface the type of organizational policies that a potential first time contributor would want to know before committing to the project.
I am curious to understand how it contributes to your decision not to integrate the tool into your workflow. I don't typically choose products based on the politics of the company that create them, which is the closest analogy I can come up with.
I am curious to understand how it contributes to your decision not to integrate the tool into your workflow. I don't typically choose products based on the politics of the company that create them, which is the closest analogy I can come up with.