GH-33977: [Dev] PR Workflow automation bot

[raulcd]

Rationale for this change

As discussed on the mailing list is quite difficult to understand the current state of a PR whether it requires further review, it has gone stale or new changes have been added. This allows us to have a set of labels based on the state of the PR.

flowchart TD
    A([New PR]):::creator
    A -- by non-committer --> B[Awaiting review]:::anyone
    A -- by committer --> C[Awaiting commiter review]:::committer
    B & C -- new review by\nanother non-committer --> C
    C & B & E  -- new committer review\nrequests changes --> D[Awaiting changes]:::creator
    D -- changes by creator --> E[Awaiting change review]:::committer
    C & E & B -- new committer review\napproves ---> F[Awaiting merge]:::committer
classDef creator stroke:#CC0;
classDef anyone stroke:#00C;
classDef committer stroke:#0C0;
classDef triager stroke:#C0C;
linkStyle 0,1,7 stroke:#CC0,color:auto;
linkStyle 2,3 stroke:#00C,color:auto;
linkStyle 4,5,6,8,9,10 stroke:#0C0,color:auto;

What changes are included in this PR?

New workflow to trigger archery bot on the required actions. New PR Workflow bot implementation on archery that manages the GitHub events and state.
New fixtures and tests.

Are these changes tested?

There are unit tests and has been tested on my fork. Some transition examples on this PR:
raulcd#74

• Closes: [Dev] Implement automation bot for PRs #33977

[github-actions]

• Closes: [Dev] Implement automation bot for PRs #33977

[github-actions]

⚠️ GitHub issue #33977 has been automatically assigned in GitHub to PR creator.

[assignUser]

Thanks for taking this on! I have some comments but the main point is that we can skip using push in favor of using github.event.action and synchronize to detect added changes. This should allow some simplification in the python logic too :)

[raulcd]

I have reproduced the workflow logic on an environment like ours. I created a copy of arrow on an organization, created a fork and did some tests with a committer/non-committer user. The full workflow with the transitions can be seen on this PR: te-chie-la/arrow-pr-workflow-copy#17
The full workflow implementation uses GitHub actions to trigger archery bot tasks and some logic on archery to manage the transitions. The code on archery is tested with the different events and expected transitions.
@kou @assignUser I think this is ready for an initial round of reviews. The majority of the diff is due to a lot of fixtures with the event payloads being added for the tests.

[assignUser]

One change to the workflow, overall it looks good imo. The python portions also looks fine. I don't love the if else chain to compute the current state but I also don't have anything cleaner that doesn't require a bunch of useless boiler plate :D

Very much looking forward to this getting merged!

[kou]

+1

Let's try this!

[assignUser]

Thanks!

[raulcd]

+1

[ursabot]

Benchmark runs are scheduled for baseline = 6cf5e89 and contender = 68e89ac. 68e89ac is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Failed ⬇️0.67% ⬆️0.0%] test-mac-arm
[Finished ⬇️0.0% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.06% ⬆️0.16%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 68e89ac9 ec2-t3-xlarge-us-east-2
[Failed] 68e89ac9 test-mac-arm
[Finished] 68e89ac9 ursa-i9-9960x
[Finished] 68e89ac9 ursa-thinkcentre-m75q
[Finished] 6cf5e898 ec2-t3-xlarge-us-east-2
[Finished] 6cf5e898 test-mac-arm
[Finished] 6cf5e898 ursa-i9-9960x
[Finished] 6cf5e898 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java