workflows/periodic-merge: update haskell-updates PR's base branch - #523160
Conversation
Manually dispatching in your fork should still trigger the workflow to test.
adb5cf2 to
ff9cba4
Compare
|
I tested it in my fork, it seems to work as expected. Ready to go from my perspective. |
This gives us better UI in the PR by hiding the commits that are already on the base branch (mostly staging) after the periodic merge. Without this, the PR has 100s of commits listed after a few days.
ff9cba4 to
5439176
Compare
MattSturgeon
left a comment
There was a problem hiding this comment.
Diff SGTM, not tested.
That means... my test must have also been inconclusive. The workflow did at least not throw an error, but I probably did not test whether the branch was reset at all. Odd, my test PR did not show any of the merged-in commits. hmmm
Would you like to hold off merging until you've re-tested, or are you confident merging the latest revision?
Since it's a bit hard to test, even with the first commit in this PR, I'm fine with merging it as is. It can't break any existing workflow, and we should know by tomorrow whether it works :) |
|
Successfully created backport PR for |
|
Successfully created backport PR for |
|
I just tested it by triggering the 24h workflow manually - it works. #521260 is nice and tidy and only shows the merge commit, but not all the others. Nice. |
This gives us better UI in the PR by hiding the commits that are already on the base branch (mostly staging) after the periodic merge. Without this, the PR has 100s of commits listed after a few days.
Resolves / based on #521260 (comment)
Things done