Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
TLDR: We saying goodbye to our dear friend
/approve-and-merge
today.After a seed was planted by @postamar (https://airbytehq-team.slack.com/archives/C02UF50V9HA/p1696626683363899) and a longer discussion with @git-phu @bgroff @jdpgrailsdev @colesnodgrass @stephane-airbyte and @davinchia its been determined that at this point the
/approve-and-merge
command has started to hurt more than its helped.Why?
No doubt its be a useful tool and a steadfast companion.
However as of late its been responsible for a number of issues
And the biggest problem by far. Its gotten us all comfortable with subpar CI. Unnecessary tests running on docs changes, Flaky unit tests, and in some cases an excessively slow test suite.
Part of the change is to be preventative, but an equal part of removing this command is help us all notice where we can and should improve.
Why now?
Over the last 2 months we've
And we believe we're now in a much better place where the time to run CI is much more tolerable.
What do I do now?
All EM's and many Senior Engineers at Airbyte have admin merge privileges.
If there is an urgent PR ping any of them.
If its the middle of the night and youre OC, look at the secondary rotation, they are Admins, page them.
If the integration test is broken, fix it.
and if the test is a known issue and too much effort to fix inside your task ping your EM, get it merged and get the space to fix the underlying issue (or remove it).
What if I think this is stupid?
Let us know! We're going to reevaluate this decision inside of the next two weeks.