531 results found
-
Support for CodeLens Change and History
I'm actually not too sure how this works but it seems like there's an opportunity to provide in-context change history info via CodeLens. I see it with Git changes and it works pretty cool - see attached screenshots.
11 votes -
Integration with Youtrack is missing ?
Integration with Youtrack ???... and I simply hate to sing in and sign out all the time .
I hate that
1 vote -
Show changeset numbers in branch explorer
I'd like to see the changeset numbers in branch explorer in the same way they are shown in 2D version tree.
60 votes -
Unity cloud build but not in the cloud
I'm sure it might be possible if there's a way to signal a unity3d editor script to automatically build when a commit is made to a repo/branch. So imagine me taking a secondary computer and just dedicating it to holding my repository/doing unity builds. I've heard of people doing stuff like this with jenkins, but there's probably a practical reason why unity cloud build is so popular.
1 vote -
Add download progress bar for merge operationgs
Really love the progress bar when you switch changesets want to see it in more places, especially the merge from changeset screen, hard to know when my 10GB of assets that I'm merging from are finished downloading until the merge window's start popping up.
3 votes -
Possibility to undo checkout without loosing file content changes
Let the user undo a checkout without loosing the modifications themselves. The result would be a file with status "Changed".
Neither the content nor the file's timestamp should change by this operation.
Currently, undoing a checkout always results in downloading the versioned content.13 votes -
add setup option 'launch client'
When the setup is finished, the client is always started.
It's a little annoying on servers, where the client isn't setup.
So please add an option to the last page of the setup 'launch client', just like the 'launch server' that already exists.1 vote -
3 votes
-
Simple repository clone operation
When you're working in distributed mode with a local development server and want to join a project, you have a lot of work ahead with PlasticSCM.
- Open PlasticSCM, go to repositories view.
- Type in the name of your local plastic server.
- Create a new empty repository.
- Right-Click and create a workspace from that repository.
- Open that workspace.
- Go to sync replication view.
- Add your local repo as source repository.
- Add the repository which holds the project you want to join (clone to your local server) as destination repository.
- Click refresh.
- Pull the changes.
- Open your local workspace.
- Click update workspace.
…
4 votes -
Add home button to 'Branches' tab
Add the home button like the one in the Branch Explorer to the Branches tab. This makes it much easier to jump to the current branch especially when being on a higher level branch.
6 votes -
Improve vertical ordering in Branch Explorer, make use of hierarchy
The default ordering of branches in Branch Explorer could be improved. It should respect and make use of the branch hierarchy, so as not to cross lines unnecessarily.
When I have several top-level branches with some child branches each, they are not grouped together vertically in a hierarchically logical order. Instead they seem to be randomly placed (?) leading to a lot of lines crossing each other. (I always enable "Display cross-branch changeset links" which makes this more obvious.)
I think child branches should always be displayed below their immediate parent (or sibling if multiple children overlap in time).
14 votes -
Support symlinks on Windows
Please add support for Symlinks (directory junctions, reparse points, ...) on Windows.
114 votes -
Push changeset data to proxy servers after commit
Problem:
Single remote workers switching changesets with average download speeds have to wait a long time to grab new changesets for the first time when using proxy server.
Solution:
Proxy server should have the data pushed to it from the plastic server, since the remote user may not always want the changeset immediately there is plenty of time to upload before the remote user is ready to switch to it.
1 vote -
Make "Add to source control" available for ignored items
When right-clicking a Private Ignored item, the "Add to source control" action is shown but disabled (grayed out). That's frustrating as there is no real reason to disallow this!
Scenario: You have ignored all *.dll files, since you build them. However, there is a specific 3rdparty DLL that you would like to make Controlled (put under source control). To do this, you would now have to edit ignored.conf, "Add the file to source control", then undo your changes in ignored.conf. If the above command was not disabled for ignored items it would have been one click in the context menu,…
5 votes -
"annotate" restricted to a single branch
Problem:
I'm on /main and would like to know when the change of a specific piece of code has entered /main. Annotate just tells me when and where this change happened first, but it's close to impossible to track the merge path through branch explorer or revision tree.What would really help:
Just annotate on /main (or any other branch, should'nt make any difference) and tell me the /main changesets at which certain lines entered the game.3 votes -
Add option to filter latest N changesets instead of date filter, to avoid empty views
I'd like an alternative to date filters, so that views will not be empty by default if I look at a branch or a repo that has been is inactive for more than 3 months. I'd rather have a setting "Show 100(+/-) changesets". Sometimes you want to look at a certain time period, but I think more commonly you just want to limit the sheer amount of data being displayed?
This might need an addition to the "cm find" query language, to specify "the N latest changesets" etc, similar to SQL "SELECT TOP(N) ... ORDER BY ..."?
Also, an empty…
9 votes -
Add "Update Cloaked" (and "Update Forced") to Items context menu.
If i have items or xlinks specified in cloaked.conf, the only way to force an update of these is to:
either removed them from cloaked.conf before "Update workspace"
or run "cm update --cloaked <path>" from the command line.
NOTE: Contrary to old documentation, running the "cm update --forced <path>" command will not update cloaked stuff.
I suggest adding a "Update Cloaked" command to the context menu in the Items view. Maybe also an "Update Forced" command, but this is probably less important.
14 votes -
Code review per Branch compared with another Branch
Currently Plastic allows Code Review Per Branch. Problem is it shows differences between the original node from which the feature branch was created (in dev) and the head node of the feature branch.
However, this is a problem: when you update your feature branch merging updates other devs have merged in dev branch.
Why? Because all their changes also appear in the code review. So at this point is not possible to do a reasonable code review of the code in the feature branch.
The solution: Take the same approach that BitBucket takes. The code review should show only differences…36 votes -
make the download link for "you need dokan.dll" clickable
When I choose "Mount this changeset in Plastic Drive", I get a long and confusing text message because I do not yet have dokan.dll installed. The text message contains a long URL with the download location.
Even if you are not going to make the installation process automatic, you could still reduce friction by making the download URL clickable. This makes the URL stand out from the rest of the text, and makes 'the right choice' easier.
3 votes -
use the .gitignore file if it is present
Have plastic simply use the .gitignore file if it is present. Now that we support the online git repos like github bitbucket and VSO.
If you have .gitignore use that methodology and if you have .ignore use that methodology.
And maybe give user option to generate a .ignore file from a .gitignore.
21 votes
- Don't see your idea?