feat: adds unpublish release pipeline action - #5797
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
tiagoapolo
marked this pull request as ready for review
July 21, 2025 20:54
Contributor
Docker builds report
|
Zaimwa9
requested changes
Jul 22, 2025
Zaimwa9
left a comment
Contributor
There was a problem hiding this comment.
One forgotten log to remove CreateReleasePipeline.tsx:119 existingPipeline undefined, a minor type change and good to go
(and rebase to include backend)
use route context
tiagoapolo
force-pushed
the
feat/release-pipeline-unpublish-pipe
branch
from
July 22, 2025 15:17
feacbc1 to
1700e35
Compare
Zaimwa9
approved these changes
Jul 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature!Changes
#5799
How did you test this code?
use branch
clone-unpublish-pipelines-be-feCase 1 - No In-flight feature
Case 2 - In-flight feature