No way to get list of merge proposals
Bug #1253770 reported by
Francis Ginther
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Tarmac |
Fix Released
|
High
|
dobey | ||
Bug Description
This is applicable to the current upstream-
http://
Given a trunk branch, return a list of all MPs available for merging (i.e. they are approved, meet the reviewer requirements, etc.)
The idea is that we want to scan a trunk branch for available MPs, select one (perhaps a specific one to do some prioritization), do various CI operations on that branch and then merge it while ensure that the MP being merged hasn't changed. There are also workflows in which we already have the MP in hand and we just want to merge it.
Related branches
lp:~dobey/tarmac/list-approved
- Francis Ginther: Approve
- David Britton: Approve
-
Diff: 93 lines (+48/-1)3 files modifiedtarmac/bin/commands.py (+23/-1)
tarmac/bin/options.py (+18/-0)
tarmac/tests/test_commands.py (+7/-0)
Revision history for this message
| Chris Johnston (cjohnston) wrote | #1 |
Revision history for this message
| dobey (dobey) wrote Re: No way to get list of ready-to-merge proposals | #2 |
| summary: |
- Feature request: provide API to use raw tarmac features without the - workflow + No way to get list of ready-to-merge proposals |
| summary: |
- No way to get list of ready-to-merge proposals + No way to get list of merge proposals |
| description: | updated |
| Changed in tarmac: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Changed in tarmac: | |
| assignee: | nobody → Rodney Dawes (dobey) |
| status: | Confirmed → In Progress |
| Changed in tarmac: | |
| status: | In Progress → Fix Committed |
| Changed in tarmac: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We have one more use for a similar feature like this. Scan the trunk branch for available MPs that *aren't* approved (which would mean being worked on) and report those. It would also rescan them for new revisions and report that as well. This would give the ticketing system the ability to determine which branches need to have tests run against them while they are being worked on in order to provide pre-approval feedback.