Maybe don't, they keep the world from falling apart at its duct-taped seams.

You aren't giving us enough context to know whether that changelog requirement is a good one or not. But if your team has agreed on the process, either convince them to change the process, or try to understand why your (hopefully reasonable and competent) colleagues believe it's necessary.

>. But if your team has agreed on the process

what if your team is dominated by process people.

> try to understand why your (hopefully reasonable and competent) colleagues believe it's necessary.

only explanation that everyone agreed to was that "it makes it easier to see what changed"

> what if your team is dominated by process people.

If that's not your jam, consider a new job.

> only explanation that everyone agreed to was that "it makes it easier to see what changed"

Maybe it's safety critical software or there are downstream clients? Maybe it's open source? Maybe it's not actually every PR and we have an unreliable narrator? The post did start with "I hate process people", after all.

For what it's worth, I'm notoriously not a process person. But I've seen and respect stability they can bring to a team and product

dude.. i am not lying or have an option currently to change my job. I don't want to engage with you after that ridiculous accusation.

fwiw way back i used not see the point of changelogs, but after experiencing what it's like to consume a lib or use software without one, also how useful they can be when you need to know what's changed, it i've changed my view on them.

yea i can see it for software libs. This is a greenfield crud app that doesn't have any real users yet and still in a quasi-prototype stage.