Support Reporting CLA Status on Merge Queue Events
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the webhook handling for GitHub merge_group events and the merge_group payload documentation linked in the issue. Determine how CLA status can be reported for queued items without a pull-request link, including the listed commit authors; done means required CLA checks are returned for merge queue items.
Written by the indexing model from the issue text.
Description
We want to enable merge queues. But for that to work, all required checks must pass on the items in the merge queue independently of them passing on the PR. This means for the CLA check, we need to listen for items being added to the merge queue and pass back a CLA check status on them.
Notes for the implementer
This might be a bit complicated because the merge queue does not have a link back to the PR in the webhook payload: https://docs.github.com/en/webhooks/webhook-events-and-payloads#merge_group
We may need to check that the CLA check passes on the author of each commit in the merge_group instead.
- Dominant language
- Python
- Stars
- 13
- Forks
- 22
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 6
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openedx/openedx-webhooks
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
openedx/openedx-webhooks#469 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
openedx/openedx-webhooks#319 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
openedx/openedx-webhooks#312 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
openedx/openedx-webhooks#285 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
openedx/openedx-webhooks#259 ·
Maintainers usually reply within 1 day
All issues in openedx/openedx-webhooks
Similar issues
-
opensubtitlescom: provider rejects pt-PT even though its own converter maps itPossibly taken @paulo-0308 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Diaoul/subliminal#1405 ·
-
Internal ErrorOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
frappe/frappe_docker#2071 ·
Maintainers usually reply within 1 day
-
bug python
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
traceloop/openllmetry#4717 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
The-Pocket/PocketFlow#161 ·
-
comp/desktop P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#157702 ·
Maintainers usually reply within 1 day