Skip to content

Simplify CI merge queue logic #11331

Open

Description

@Jefffrey

Is your feature request related to a problem or challenge?

#11097 introduced merge queues. This issue is for some potential followup work to see if we can simplify things, where possible.

Describe the solution you'd like

Things to look into:

  • Is there a way to achieve the python script logic in a simpler way, possibly without needing python scripts at all?
    • Related to triggering only the necessary suites
  • Try to centralize the dispatch logic: currently the logic for triggering a suite is located within paths.yaml, ci.yml as well as the python scripts (e.g. for miri) which is confusing, can we try put it in a single location?
  • Reconsider need for the cache-refresh-only logic; how much do we gain from these caches, does it make the complexity in our CI code worth it?

Describe alternatives you've considered

No response

Additional context

See discussion in original PR for more context as to some of these points

Activity

  1. added theissue type on Oct 2, 2026
  2. added
    development-processInternal changes; PRs with this label are excluded from changelog
    on Oct 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    development-processInternal changes; PRs with this label are excluded from changelogenhancementNew feature/addition

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions