Settings and activity
12 results found
-
3 votes
Rando Wiltschek shared this idea ·
-
3 votes
Rando Wiltschek shared this idea ·
-
3 votes
Rando Wiltschek shared this idea ·
-
24 votes
Rando Wiltschek supported this idea ·
-
22 votes
An error occurred while saving the comment Rando Wiltschek supported this idea ·
-
3 votes
An error occurred while saving the comment Rando Wiltschek commented
Yeah, I suppose so. A quick way to sort small changesets into the correct branches.
In plastic I can't easily switch to the right branch, commit my fix and move back, since I have to undo all my changes in order to switch.
Without that limitation (it never was an issue for me with mercurial and SourceTree), it wouldn't be necessary, I suppose.
Rando Wiltschek shared this idea ·
-
34 votes
An error occurred while saving the comment Rando Wiltschek commented
I thought so, but I couldn't find the suggestion.
Rando Wiltschek shared this idea ·
-
42 votes
Rando Wiltschek supported this idea ·
-
6 votes
An error occurred while saving the comment Rando Wiltschek commented
Ah, I get you. Although given the overloaded context menu that we currently have, I don't think another option will be faster than double clicking a changeset and clicking "I'm sure".
But maybe holding shift like with the windows delete function might be a good compromise for experienced developers who need this often.An error occurred while saving the comment Rando Wiltschek commented
I don't quite understand how your suggestion is different. Can you elaborate?
Rando Wiltschek shared this idea ·
-
3 votes
Rando Wiltschek shared this idea ·
-
6 votes
An error occurred while saving the comment Rando Wiltschek commented
Great, thanks!
Rando Wiltschek shared this idea ·
-
4 votes
An error occurred while saving the comment Rando Wiltschek commented
I second this. Maybe optionally (per attribute) without the attribute name. For example, I'd like to see the "status" attribute as soon as it has any value: E.g. just "Done" or "Rejected".
In the plastic guide book the attributes are actually shown in the generalized examples. That's more or less exactly what I'd want.
Also having a color per attribute type (or even value?) would be useful too. So we can have "status = done" in green or "status = rejected" in red, and so on.
Rando Wiltschek supported this idea ·
This would be very useful.
Not being able to switch branches with uncommitted changes like you can in Git/Mercurial is a tremendous burden that costs us a lot of time.