Something that happens quite often in my daily work is forgetting to do something silly, for example, finishing a feature and after checking it on plastic I notice that I`ve forgotten to save the scene or move some script to another folder, something on those lines, but now I have a changeset that represents my last work and its followed by a changeset that is just noise. As we tend to commit often these errors end up causing a bunch of noise in our branch explorer. So my question is, do I have some operation to mix those changesets?
Hi,
I’m afraid Plastic doesn’t support rewriting the history of the repository.
Are you following a single-branch workflow? Or a task per branch workflow?
Regards,
Carlos.
On task per branch
Hi,
If you are working on task branches, and assuming you are the only person working in your branch, you shouldn’t be afraid of performing frequent checkins, even if they are “noise”.
Once the branch is reviewed and merged into the main line, it should be transparent for the rest of the team.
In Plastic, you can delete changesets or use the subtractive merge to “disintegrate” changesets: Plastic SCM - Advanced version control guide
Regards,
Carlos.
Yap, the noise exists on the branch task only, the main is clean. I thought that we had a simple way to mix some of the last commits, then I could end with a cleaner task branch, but it’s not a thing that prevents me to work on it anyway. Thanks for ur time