At work I use Jenkins, and I am very frustrated with it. I've worked with GitHub Actions, GitLab CI, and Azure Pipelines, and none were truly enjoyable to work with. They're acceptable.
The last change I made on our project was to send a build failure and build fix notification email on branches to the last committer. (After having disabled branch build failure notification emails because Jenkins (or its plugins) were not able to send to only the branch developer/new change pusher/author a while ago.)
The best thing we did was introducing commit message conventions and convco to verify them, and to generate changelogs automatically.
It is warranted, and your colleagues seem to agree.
and other people on the team will almost always agree that it’s a good idea and will happily accept my PRs
I think you may be misinterpreting what is happening.
Them not taking initiative does not correlate to its importance. It’s just that most people don’t take initiative - or at least here, evidently, for naming consistency.
How much of an issue ambiguous naming is or may become depends on context - on a lot of things. But ambiguity in naming, just like elsewhere, weakens certainty and reasonability. If you can define and keep clear terminology, then always do so.
09:30 on my team. Between multiple project teams I believe our dailies are between 9:00, maybe slightly before too, and 10:00. Can also depend on the customer if we're part of their development team. I believe not all teams have them every day.
It's a good time for me because I sometimes begin at around 9:00.
At 9:00 begins our central working hours where we're expected to be working. And I think that's late enough for the late starters. So I like where we're at.
I think it's good to have it "early" rather than late. If you struggled the previous day it's a good point of fresh start and possible discussion or follow-up support. It's also where you have [to make] a plan for the day.
At work I use Jenkins, and I am very frustrated with it. I've worked with GitHub Actions, GitLab CI, and Azure Pipelines, and none were truly enjoyable to work with. They're acceptable.
The last change I made on our project was to send a build failure and build fix notification email on branches to the last committer. (After having disabled branch build failure notification emails because Jenkins (or its plugins) were not able to send to only the branch developer/new change pusher/author a while ago.)
The best thing we did was introducing commit message conventions and convco to verify them, and to generate changelogs automatically.