action #76738
Updated by livdywan about 4 years ago
## Motivation Although we ~~use~~tried out **Mergify** use Mergify to rebase branches¹ branches before merging by default, this only applies when there's already two approvals and all tests pass. Unrelated failures that are fixed in another branch or dependency updates will leave such PRs in a failed state that requires a manual rebase. We could save time checking the state of branches if branches were be rebased automatically². automatically*. ## Suggestions - Use a GitHub action to automatically rebase outdated branches https://github.com/marketplace/actions/auto-rebase - Consider labels to decide if branches should be rebased --- * ¹ Mergify wasn't working very well as-is: https://github.com/os-autoinst/openQA/pull/3585 * ² Note: There are other actions that implement "automatic rebases" and the same phrasing is sometimes used to mean rebase triggered by writing a special comment. This ticket is about behavior that requires no human intervention.