batches: support `replaceBatchSpecInput` with existing draft batch change

Review changes
Download
Patches
Plain diff

Closed batches: support `replaceBatchSpecInput` with existing draft batch change

kr/replace-batch-spec-input-with-existing-batch-change-2 into main

Overview 3
Commits 8
Pipelines 0
Changes 3

Closed Warren Gifford requested to merge kr/replace-batch-spec-input-with-existing-batch-change-2 into main 3 years ago

Overview 3
Commits 8
Pipelines 0
Changes 3

Created by: courier-new

Supersedes #28827 (and to a lesser extent, #28825, until we resolve what to do for executing a new batch spec on a non-draft batch change).

Updates replaceBatchSpecInput to re-associate the previous batch spec's batch change with the new one that is replacing it, but only if the batch change was still a draft. It will produce an error if you attempt to call it with a batch spec that was already applied to a batch change.

To do so, I stole BatchChange.IsDraft that Thorsten wrote from #28840.

Merge request reports

Activity

Filter activity

Approvals
Assignees & reviewers
Comments (from bots)
Comments (from users)
Commits & branches
Edits
Labels
Lock status
Mentions
Merge request status
Tracking

Please register or sign in to reply

0 Assignees

None

Select assignees

0 Reviewers

None

Request review from

Labels

cla-signed server-side team/batchers

Select labels

Manage project labels

Milestone

None

Time tracking

No estimate or time spent

2 Participants

There are currently no pipelines.

To run a merge request pipeline, the jobs in the CI/CD configuration file must be configured to run in merge request pipelines and you must have sufficient permissions in the source project.