Enhace Article Revision History with Interactive Rebase Functionality
Haripriya Manoharan
It would be great to have a similar functionality as Git-Rebase. Git rebase is a command used in Git version control systems to incorporate changes from one branch into another. Unlike merging, which creates a new commit to combine the changes of two branches, rebasing rewrites the commit history by moving or "replaying" commits from one branch to another.
- Keep our commit history tidy and easy to understand.
- Avoid cluttering our history with unnecessary merge commits.
- Reduce the likelihood of conflicts when merging branches.
- Make code reviews smoother by presenting changes in a logical order.
- Enable better collaboration by keeping everyone's work organized and up-to-date with the main branch.
Log In
Sara Halper
Thiru , Haripriya Manoharan,
I often have a published version that needs a hotfix while there is already a WIP version in the works for the next version.
The hotfix is based on the current published version but I want to rebase the WIP version to continue working on the updates for the next version.
Currently this workflow is not supported. It is cumbersome and manual effort to push the hotfix and copy-paste the new revisions for the next version.
Thiru
Sara Halper thanks for your sharing your idea. Would like to confirm that you expect our article revision history information / workflow to function like Git-Rebase?
May we know the pain points you feel from in our current revision history?
Thanks Haripriya Manoharan raising the request on behalf of the customer.
Haripriya Manoharan
This feature request is raised on behalf of Sara Halper.