526 results found
1) highlight the current file revision in the history list GUI & command line as selected by the workspace (I had a feeling it was bold but isn't in 188.8.131.521). If the workspace revision is modified, the parent should still be highlighted.
2) give an indication of which revisions have been merged in the history list (eg. a column for number of branches seeing this revision; merged yes/no)
3) populate the 'Properties' panel when selecting items in the 'Version tree' (it is blank regardless of which branch or cs I select, and many of the cs numbers and names on…9 votes
It woul be useful to have the option to export files differences in the unix diff format62 votes
I would love the ability to select a new button "auto comment" from Checkin Comments drop-down on the Checkin UI that would use the the semantic code engine to generate comment lines like the following:
-added update methods to InquiryRepository
-added Username parameter to SetReferralDelivered() in ReferralService
-deleted class MyFakeClass
-created new enumeration MyFakeEnum
this would be the basis of every checkin comment and then the developer could add to it with specifics or just modify the text to be more explicit or supply reasoning or whatever.6 votes
To avoid mistakenly adding multiple xlink targets to the same source when creating sync views and to make sync view creation to repos with xlinks easier I suggest that the sync view editor should be "target" centric, not "source" centric:
I click add new sync view.
Instead of clicking add new source as I am supposed to now, I click "add new target".
I choose the target on a target server.
Plastic detects that I already have a repo with the same name on my source server (or use some other similarity measure as I have suggested above) and ask…7 votes
In branch explorer, allow a changset to be dragged from one branch to another to merge it whereever you want.
This would make merges much slicker, by saving all of the RMB clicking.23 votes
Right now there is no mechanism to prevent users from deleting code reviews (unless I've missed something obvious), which is a problem for what we're trying to do. If nothing else it would be nice to have a "before-rmreview" trigger that we can hook into14 votes
I find myself repeatedly typing in a lot of the same comments. I would like to auto populate the the commit comment with what was used to create the branch.71 votes
When viewing the "Pending Changes" in Visual Studio plugin, double clicking a 'changed' item opens the 'Diff view'.
I think that when you double click a file it should open the file editor. This will make the behavior more consistent with Visual Studio in general and with the behavior of double clicking an 'added file'...
It will also make it more consistent with the behavior of other source controls, making the transition to Plastic even smoother.9 votes
Currently there are merge and diff scripts available for xls(x), doc(x) and ppt(x) files, but more and more European organizations are moving to Open Document Format files as their standard.4 votes
Add a switch to the command line tool that gives the same functionality as the GUI tool's "Synchronize All" function. Additionally, give [both] the ability to synchronize all views at the same time.
This would allow easier scripting of "backups" to a central server.50 votes
in the branch explorer, have the ability to specify a replication source, instead of having to pull a branch from a source before it showing up in the list.
This way it would be easy to add all the local developer repos as replication sources to a new team members BrEx in a distributed scenario, without having to pull something from every local developer repo.7 votes
Icons in Windows Explorer for files that are currently added to source control but haven't yet been checked in.3 votes
This would help people learn syntax i think.25 votes
A plugin to allow integration of the following features in SSMS:
-revision history on a file
-branch explorer3 votes
please, add a number behind the code review menu item which shows the user how many active code reviews are assigned to him.
Maybe it could even flash up a bit when there are new reviews.20 votes
There are many branching scenarios that people use. But it would be nice to have a default template. And template libraries.
Example when I create a repo I also rename main to Production and create Test and Development branches.3 votes
It would be useful to be able to set a flag on a changset such that it won't be merged from the branch it exists on (by merging from a subsequent changeset, although cherry picking it could possibly be an exception).
I sometimes need to make temporary changes on a branch (eg. for testing), but don't want to risk these getting merged upstream.
Normally I do periodic checkins of all changed files, so need to be careful to exclude these. It would be nice for the temporary changes to be managed by the SCM in a safe way.
I don't…3 votes
Support for LDAP queries (including OR operator) that would allow better specificity in configuring access control to repo server.
Screenshot of config wizard: http://screencast.com/t/uXZVgpUvV2 votes
If you search for a changeset and it is not found, nothing happens. There could be several reasons:
1) the changeset does not exist
2) it is hidden due to 'display only relevant changesets'
3) it is a recent addition and you need to refresh the view first
It would be helpful if a dialog was shown with the reason, with perhaps an option to do either 2) or 3) and then find it.7 votes
Usually I would not like to group changes from a merge (rebase) with those from editing files (development). I would like to be prevented from making this mistake and checking it in before realising.
There is already a similar option when switching/updating the workspace: "Do not allow, show an error". Could it be extended to cover merges, or a new option added?5 votes
- Don't see your idea?