Search the Community
Showing results for tags 'change'.
Found 2 results
I spend the last week's to build this simple dotnet Core app: https://github.com/KhaosCoders/plastic-notify-center It acts as notification hub where triggers from Plastic SCM get translated into notifications for users who registered for them. Currently it only sends emails via SMTP, but it is prepared to support more channels. There sure is room for improvement, too. Feel free to suggest or implement new features. I hope the guys from Codice Software don't mind that the icon is similar to the plastic icon. (I'll change it of course if you do mind it) Please feel free to use it, it's free ;)
When a workspace has pending changes and the branch it is on has newer commits, the GUI provides the View New Changes button, allowing the changes to persist and resolve against the changes made. This is useful, as it doesn't require a new changeset to be created and local changes are retained. Does such functionality exist for branch switching? Often in our workflow, there are a common set of changes that can occur locally that prevent us from discarding if we want to switch to a neighbouring branch. It seems that such a workspace change would follow the similar process of resolving the changes without necessitating a commit, is that correct? Possibly a command line option could resolve this outside of the GUI also.