Ability to remove PR's from a created release
WHen working with pipelines, when we create a release and we merge PR's to the release so we can then deploy later, it would be nice if we have the option to remove them in case someone change their mind instead of cancell release and srtart over
Indoberto Lerma
shared this idea
-
Akash Dhabe
commented
This is a much needed one. We have more than 50 features in our releases. Carefully selecting them one by one, based on which once are approved , in the first go itself is a big task. To have to abandon entire release if one of them receives a no-go at the last moment means delaying the release.
-
Scott Bradley
commented
I just hit this same issue. This is an efficiency killer when you have one feature that needs to be pulled out of a release, either because it needs to go early, or because an issue has been found and it needs to be pulled out. I understand from a git perspective that behind the scenes we probably still need to abandon the old release and create a new one, but if there are 30 items queued up for release, having to re-assemble from scratch rather than copying from the abandoned release is wasted time for our beloved devops folks!
-
Kyle Varga
commented
Issue I see with this is that without a force-push you cant remove that commit from history of release branch. We would want functionality to automate creating a new release branch and abandoning the old one. Vs abanoning the old one and re-creating (and having to stop a bunch of validations from re-running.
-
Jonathan Flatt commented
Would be very useful. When releases get large it's quite cumbersome to abandon a release and re-create.