Changelog bot is out of control

[bonomat]

Problem

Reminding us to update the changelog file is not helpful and sometimes this bot does what it wants.

Goal

Prevent Skynet early!!!111

Examples

#2330

Tasks:

• Remove mergify-changelog bot
• Make basecamp announcement that breaking/notable changes should be detected during grooming and it should be indicated in the ticket if the changelog should be updated. The Scrum Master should take this step up in grooming.

[D4nte]

Apologies, I did not read the tasks during grooming:

Make basecamp announcement that breaking/notable changes should be detected during grooming and it should be indicated in the ticket if the changelog should be updated. The Scrum Master should take this step up in grooming.

I disagree on this point, we do not need team consensus to decide what should or should not be in the changelog. It should be part of a normal PR to have changelog update (if relevant).

• Is the new code tested?
• Is the changelog updated?

Should be questions that dev and reviewers ask themselves on a given PR.

Happy to remove the bot but not keen to have a heavy process to decide to update the changelog.

[bonomat]

It's been a while that I wrote this. I assume I was in the role of the scrum master and was writing this without debating it 😬

I think it was not my intended to introduce new processes but the idea was that during grooming we mention something ala "Hey, watch-out, this ticket will introduce changes which should be mentioned in the changelog"

@da-kami : somehow I have the feeling you could shed some more light on this :)

[da-kami]

(We started by questioning changelog bot because we could agree that we almost always ignore it, because it is just too annoying to have this in every PR. Then we thought about "how could we do this PR specific" and reached the conclusion that this is not really feasible.)

The basic idea behind the proposal to "add this to grooming" is to raise the awareness of having breaking changes in tickets.
This would be a concern of grooming. Team consensus might not be especially relevant, but being aware that a ticket includes breaking changes it of interest.

That said, I would not see a "hard" process around this, but a soft one. If we already are aware of a breaking change being introduced in a ticket we could add a note to the ticket recommendation to consider a changelog update. This does NOT mean that we would "carefully evaluate" that for every ticket.