Rollback

Rollback the master branch to the previous commit

67 followers

Rollback the master branch to the previous commit

67 followers

Visit website

Git clients

A github action to manually rollback the master branch to the previous commit, creating a timestamped backup branch for recovery.

Free

Launch tags:Productivity•Developer Tools•GitHub

Launch Team

ElevenAgents by ElevenLabs — Scale conversations without scaling your team

Scale conversations without scaling your team

Promoted

buildpipe

Maker

📌

A github action to manually rollback the master branch to the previous commit, creating a timestamped backup branch for recovery. ⚠ Warning This action force pushes to the master branch, which can cause issues for other collaborators. Use with caution and ensure you understand the implications of removing a commit before proceeding. This action is for developers and teams who want and immediate rollback of their master branch. Running this action will change master and rewrite the commit history. Changes will be lost forever. Be very careful and sure whe you use this. DO NOT use this action if you are still unclear as to what this does. Why ? Its so common that we mess up or do a bad commit / merge on the master branch and we want to rollback production. It causes panic and frustration. Using this action anyone in the team who has permissions on the repo can perform a rollback of the master branch. It can save time and be very handy when under a lot of stress. How it works: The action checks if it's running as a workflow dispatch event. If not, it exits with an error. The action authenticates with GitHub using the provided token. The repository is cloned, and the action checks if the current branch is master. If not, it exits with an error. A new backup branch with a timestamp in its name is created and pushed to the remote repository. The master branch is rolled back to the previous commit, and the updated master branch is force pushed to the remote repository. The action cleans up the temporary repository directory. Limitations and Potential Issues: Force pushing: Force pushing to the master branch is generally discouraged, as it can cause confusion and issues for other collaborators. Loss of history: Since the action erases the history of the current commit, you may lose important changes or context if you do not carefully review the backup branch before using this action. Limited to the master branch: This action is hardcoded to work only on the master branch. You may need to modify the action to support different branch names or make the branch name configurable. Permission issues: The action requires a GitHub token with sufficient permissions to clone the repository, create and push branches, and force push to the master branch. If the token does not have the required permissions, the action will fail.

Report

2yr ago

@raiyanyahya A GitHub action for manual rollback with timestamped backup sounds like a valuable tool for ensuring code safety and recovery. Great work on creating this solution! Congrats guys!

Report

2yr ago

buildpipe

Maker

@tornike_tsiramua1 thank you!

Report

2yr ago

SyncSignature

@raiyanyahya Developer tools have the highest potential of succeeding over here since PH community has a majority of makers. Good luck with your launch today!

Report

2yr ago

buildpipe

Maker

@neelptl2602 thank you!

Report

2yr ago

Crustdata

Congrats Team Rollback on your epic launch on Producthunt! Your Github action is an interesting tool to effectively rollback the master branch. Just a thought - Could there be an additional future feature of rollback with user-defined commits, that way the user has more control over what version they would want to fall back to, not just the immediate previous one. Keep up the splendid work!

Report

2yr ago

buildpipe

Maker

@manmohit thats a great idea. i willl add it to version 2

Report

2yr ago

MoneyVision

Cool idea, but: Does this reset the master/main branch? Rewriting the git history for the master branch will most likely mess up the local branch for everyone working on this project and all of their other branches. Why not just revert the last commit? Saves you a lot of trouble. "git revert HEAD"

Report

2yr ago

buildpipe

Maker

@timobechtel yes you are right. the main reason for doing this is urgency, directly from a github action. Typically you would not run this on a project worked on by many people. This is for quick production deploy rollbacks but yes this is discouraged. I wrote the same in the description.

Report

2yr ago

MoneyVision

@raiyanyahya You clearly added a lot of warnings :) You probably know what you are doing, but others might not. That's why I felt the urge to write this comment.

Report

2yr ago