Skip to content

Conversation

@JaroslavTulach
Copy link
Member

Pull Request Description

  • using "CI: Keep up to date" is a "no, no" as it puts too much pressure on our CI
  • however I like to use it as one shot action
    • add the label
    • wait for CI to pick it up and merge develop into the PR
    • remove the label
  • why not optimize for this scenario?
    • solves the "pressure problem"
    • makes the label useful

Important Notes

@JaroslavTulach JaroslavTulach self-assigned this Nov 13, 2025
@JaroslavTulach JaroslavTulach added the CI: No changelog needed Do not require a changelog entry for this PR. label Nov 13, 2025
@JaroslavTulach JaroslavTulach added the CI: Keep up to date Automatically update this PR to the latest develop. label Nov 13, 2025
@JaroslavTulach
Copy link
Member Author

  • Guys, what do you think about this change?
  • It cannot hurt to integrate it, can it?

@hubertp
Copy link
Collaborator

hubertp commented Nov 18, 2025

I don't know what is the purpose of the label if it doesn't keep up date, as it says.
Personally, I'd prefer we remove this mechanism all together, it has served its purpose but is currently doing more damage than good.

@JaroslavTulach
Copy link
Member Author

JaroslavTulach commented Nov 18, 2025

Thanks for the review.

I don't know what is the purpose of the label if it doesn't keep up date, as it says.

It keeps up to date. Once.

... currently doing more damage than good.

That's why this PR intends to fix the core of the problem while keeping the overall goodness.

@hubertp hubertp removed the CI: Keep up to date Automatically update this PR to the latest develop. label Nov 19, 2025
@hubertp
Copy link
Collaborator

hubertp commented Nov 19, 2025

Removed the label as this is eating up resources.

That's why this PR intends to fix the core of the problem while keeping the overall goodness.

The core of the problem is somewhere else (aka identifying underlying CI issues and fixing them one by one which takes time). This label continues to feel like a poor band-aid and adding some custom behaviour doesn't help.

@JaroslavTulach
Copy link
Member Author

JaroslavTulach commented Nov 21, 2025

Removed the label ... (manually)

  • The change in this PR is supposed to remove the label automatically!
  • that's apparently not happening right now
  • it is hard to test/debug these 3rd party GitHub integration
    • do I need some administrative priviledges to see what exactly mergify does?
  • the simplest way to find out if this works is to integrate this PR and see

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI: No changelog needed Do not require a changelog entry for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants