rollback-ticket

To rollback a merged ticket on a Git CP branch, the workflow identifies the merge, validates the ticket status, switches to the CP branch, and reverts the merge. It requires user confirmation before proceeding to ensure safety.

You need to revert a ticket merge from the CP branch when post-merge issues arise that require undoing a change. This rollback process ensures stability by safely removing problematic code introduced by the specific ticket merge.

Yes, the Git rollback process runs tests after reverting the merge to ensure stability. It also updates the ticket status documentation accordingly to maintain project traceability after the revert operation completes.

No, you cannot use this ticket rollback workflow to modify the main or master branch. The safety-first approach strictly avoids modifying main or master branches and focuses solely on reverting changes on the CP branch.

To start a rollback for a ticket merge on the CP branch, you need to supply the TICKET-ID and the feature slug. The workflow then prompts for user confirmation before proceeding with the actual Git revert operation.