Skip to content
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

Improvements to check-merge action #15883

Merged
merged 2 commits into from
Jul 9, 2023
Merged

Conversation

barrettj12
Copy link
Contributor

@barrettj12 barrettj12 commented Jul 9, 2023

Notify the committer instead of the commit author. This should fix the case where e.g. person X (committer) backports person Y's (author) commits. Person X should be notified here.

Furthermore, for each commit, check if it is already part of an open merge, and skip in this case.

Finally, some small QoL improvements to error log formatting.

Tested my changes locally and here.

- add String() function to executeResults
- add GITHUB_TOKEN to workflow
@barrettj12
Copy link
Contributor Author

/merge

@jujubot jujubot merged commit 73a6bb6 into juju:2.9 Jul 9, 2023
19 of 20 checks passed
@barrettj12 barrettj12 deleted the merge-check-committer branch July 9, 2023 22:37
@barrettj12 barrettj12 mentioned this pull request Jul 9, 2023
jujubot added a commit that referenced this pull request Jul 9, 2023
#15884

Merges the following patches:
- #15883
- #15876

### Conflicts
- tests/suites/model/multi.sh
@barrettj12 barrettj12 mentioned this pull request Jul 10, 2023
jujubot added a commit that referenced this pull request Jul 10, 2023
#15886

Merges the following patches:
- #15884
- #15883
- #15727
- #15876

### Conflicts
- migration/precheck_test.go
- upgrades/upgradevalidation/migrate_test.go
@barrettj12 barrettj12 mentioned this pull request Jul 10, 2023
jujubot added a commit that referenced this pull request Jul 11, 2023
@hpidcock hpidcock mentioned this pull request Jul 11, 2023
jujubot added a commit that referenced this pull request Jul 11, 2023
#15896

Forward ports:
- #15845
- #15725
- #15852
- #15854
- #15849
- #15855
- #15857
- #15861
- #15862
- #15860
- #15864
- #15825
- #15866
- #15863
- #15870
- #15871
- #15872
- #15873
- #15874
- #15876
- #15875
- #15881
- #15727
- #15883
- #15884
- #15880
- #15879
- #15886
- #15887
- #15877
- #15888
- #15893
- #15894

Conflicts:
- cmd/juju/ssh/debugcode_test.go
- cmd/juju/ssh/debughooks_test.go
- cmd/juju/ssh/scp_unix_test.go
- cmd/juju/ssh/ssh_machine.go
- cmd/juju/ssh/ssh_machine_test.go
- cmd/juju/ssh/ssh_unix_test.go
- worker/dbaccessor/worker.go
- caas/kubernetes/provider/k8s_test.go
- caas/kubernetes/provider/operator_test.go
- caas/kubernetes/provider/package_test.go
- caas/kubernetes/provider/rbac.go
- cmd/juju/application/deployer/bundlehandler.go
- cmd/juju/application/deployer/bundlehandler_test.go
- cmd/jujud/agent/model/manifolds.go
- core/bundle/changes/changes.go
- worker/caasapplicationprovisioner/application.go
- worker/caasapplicationprovisioner/application_test.go
- worker/caasapplicationprovisioner/mock_test.go
jujubot added a commit that referenced this pull request Jul 19, 2023
#15951

#15883 improved the "check for merge conflicts" action so that it won't notify about commits that are in an open PR. However, we just noticed a race condition where the 2.9 -> 3.1 merge PR landed while the check was running. We must have:
- Pulled the 3.1 branch _before_ the PR landed
- Seen the commit wasn't in 3.1
- Checked for open PRs _after_ the merge PR landed - so we didn't find any.

Easy fix - we just check for PRs that are open|merged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants