Merge queues
Metadata
Current evaluation
Maintainer tracking issue to try out GitHub merge queues (prototype in charmcraft#1676). Idle876 days: no merge_group trigger added, no documented configuration, and CI has since moved to shared starflow workflows.
Suggested action: needs triage
Reason: Zero labels, zero comments, zero activity for 876 days, and no assignee — there is no sign this has been categorised or prioritised, and the author's own plan ('Once we're comfortable with specific configuration, I'll document that here') never happened: grep for 'merge_group' and 'queue' returns no matches in starbase or starflow, and qa.yaml still only triggers on push/pull_request. The referenced charmcraft#1676 prototype is merged, so the exploratory work exists but no configuration decision was ever carried over, and commit a411e24 ('ci: use starflow CI actions') moved CI to shared reusable workflows, making it ambiguous where the change should now live — this needs a maintainer decision on whether to pursue it, not an automatic close.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
8
Complexity:
30
Confidence:
65
Actionability:
40
|
needs triage | Maintainer tracking issue to try out GitHub merge queues (prototype in charmcraft#1676). Idle876 days: no merge_group trigger added, no documented configuration, and CI has since moved to shared starflow workflows. | |
| qwen/qwen3.6-35b-a3b |
Impact:
10
Quick Win:
7
Complexity:
5
Confidence:
85
Actionability:
70
|
close resolved | Tracking issue for experimenting with GitHub merge queues. Referenced PR #1676 was merged to enable CI checks on merge groups. No follow-up activity for 866 days. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
17
Staleness:
92
Complexity:
15
Confidence:
78
Support Request:
5
|
close stale | Tracking issue for adopting GitHub merge queues, created by maintainer lengau 845 days ago referencing charmcraft PR #1676. No comments, no follow-up documentation, and no merge queue configuration found in the starbase repo. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
92
Complexity:
25
Confidence:
85
Support Request:
5
|
close stale | Tracking issue for implementing and documenting GitHub merge queue configuration. Created by a maintainer over two years ago with no comments or updates, currently awaiting configuration finalization and documentation. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
10
Confidence:
85
Support Request:
0
|
close stale | Tracking issue for implementing GitHub merge queues. Proposed by a maintainer two years ago with no comments, labels, or follow-up activity. Awaiting documentation and upstream changes. |
Update history
No update history recorded yet.
Related work
-
Related To:
charmcraft#1676
(confidence 70%)
The prototype PR linked in the body; tracker notes it was merged to enable CI checks on merge groups, but no equivalent config landed in starbase.
-
Related To:
starbase#272
(confidence 55%)
Commit a411e24 'ci: use starflow CI actions (#272)' migrated QA to shared reusable workflows, so merge_group triggers may now belong in starflow rather than starbase.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1676 ci: enable merge groups for CI | charmcraft | merged | Merged as commit 1762b90b, adding merge_group triggers to Charmcraft's CI workflows (3 files, +5/-1) so PR checks also run in merge groups — an initial step toward a merge queue. |