Well … there are 2 groups:

1. In work it’s up to owner/team, so I … “don’t care” … However this sounds “it is how it is” …
2. When working on project I own then I use all code tools locally anyway, so there’s also no need to spend extra time on CI especially when pushing simplest fixes (having in mind I already check it locally).

When something is really important for me or I’m just not sure I use a virtual machine, so anyway I check everything locally … I would say that CI is good to force some standards in team or in some edge-cases when you can’t do something locally.

It’s really more about habits, for example before pushing commit some script may automatically run to ensure all checks are passing, but alternatively you can do the very same job on CI.

Based on above CI is especially useful when you don’t work with a close team you trust, but with a “random contributor”, so you don’t have to pull each fork of your code and run checks locally, so it means a lot when you work on a big open source project with many maintainers and within your team it’s up to you or the owner what preferences are desired.