-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto rebase workflow addition #1152
Auto rebase workflow addition #1152
Conversation
@plebhash @jbesraa @rrybarczyk this PR is my proposal related to discussion we had during last PR-review-club call. |
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 1 ALERT: Threshold Boundary Limit exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 4 ALERTS: Threshold Boundary Limits exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 1 ALERT: Threshold Boundary Limit exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
This looks good |
aside from the PRs listed on the description, there's also this one: GitGab19#23 |
Goal
The goal of this PR is to better manage the situation in which every time we merge a PR against
main
, all the others become outdated, and we need to ask PR authors to rebase them.main
into PR's branch, but that's not ideal since we would add a merge commit only for this, which will be tracked in the git history forever.Solution
This PR adds a new workflow file which is executed every time we push something to main (so after we merge a PR).
ready-to-be-merged
, and automatically rebase them, without leading to the "co-authoring" issue described before.Examples
To better understand what this PR looks like, I recommend to take a look at my fork, specifically at: