526 results found

1. Context menu: Merge to this branch/changeset...

   Currently, when I'm on a branch and I want to merge what I have to another branch (e.g. main) I have to right-click on my current branch/changeset, select "merge from this [] to..." and then pick the target from an endless list of all my braches.

   This is incredibly error-prone, but still somewhat faster and more convenient than switching to the target branch and then merging from the branch I've just been at.

   What I'd like to see is when I right-click on another branch/changeset (that I'm not on) that I get the option "Merge to this branch/changeset...".

   This might seem like a small improvement, but given how often we do this, it'd definitely help. An option setting to also then switch to the target branch when doing this might be a plus (I noticed someone else asked for this before).

   Our usual workflow is to first merge from main to the current branch, sort out merge conflicts, check the build, etc., commit fixes and changes if needed, and then merge back to main.

   Currently, when I'm on a branch and I want to merge what I have to another branch (e.g. main) I have to right-click on my current branch/changeset, select "merge from this [] to..." and then pick the target from an endless list of all my braches.

   This is incredibly error-prone, but still somewhat faster and more convenient than switching to the target branch and then merging from the branch I've just been at.

   What I'd like to see is when I right-click on another branch/changeset (that I'm not on) that I get the option "Merge to this branch/changeset...".

   This might… more

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Provide changeset-id's in update triggers

   Now, the update triggers only provide a path to the workspace being updated.
   Having access to the old and new changeset-id's opens up quite a lot new possibilities.

   For example, in UE4, when working with plugins in a code project, they are compiled automatically at first. When making code changes to the plugins, they are often not automatically detected which causes the engine to crash at startup.
   Deleting two specific folders makes the engine recompile those binaries automatically and thus fixes this inconvenience. Unfortunately, this process takes about 5 minutes on average so doing it after every update is not feasible.
   By providing a specific string/tag in the comment of checkins that require a compile, we are able to only recompile when necessary.

   In order to make this work, we have to write out the current changeset-id to a file in the before-update trigger. Then in the after update trigger, we get the current one. Finally we would use the find command to get all changesets in between those two and check if any of their comments contain the tag.

   We are already able to access the current changeset-id with
   cm status --nochanges
   and some parsing. (Although this could be made easier.)
   Thus, only exposing the future changeset-id in before-update and the previous changeset-id in after-update would suffice.

   Thanks in advance

   Now, the update triggers only provide a path to the workspace being updated.
   Having access to the old and new changeset-id's opens up quite a lot new possibilities.

   For example, in UE4, when working with plugins in a code project, they are compiled automatically at first. When making code changes to the plugins, they are often not automatically detected which causes the engine to crash at startup.
   Deleting two specific folders makes the engine recompile those binaries automatically and thus fixes this inconvenience. Unfortunately, this process takes about 5 minutes on average so doing it after every update is not… more

   15 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Allow for display of branch attributes in the branch explorer window

   In the branch explorer view you have essentially two sections. The graphical chart on the left and the properties panels on the right.

   Assigning attributes to branches is very handy for keeping track of things like status and work type, but currently you can't see those attributes "in a big picture" as you have to click on the branch and then look at its attributes in the right hand panel.

   What about allowing us a Display Option to draw the attribute name and value in the main chart right underneath the branch? This would allow for seeing the information on multiple branches at a glance and help with the big picture.

   In the branch explorer view you have essentially two sections. The graphical chart on the left and the properties panels on the right.

   Assigning attributes to branches is very handy for keeping track of things like status and work type, but currently you can't see those attributes "in a big picture" as you have to click on the branch and then look at its attributes in the right hand panel.

   What about allowing us a Display Option to draw the attribute name and value in the main chart right underneath the branch? This would allow for seeing the information on… more

   4 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. "Hidden changes" should not cause an error dialog when used properly

   Some configuration files & libraries etc. can need to be present, but customized/recompiled per-developer.

   We want to commit them to the repository (as they DO need to be present in at least a "default" state), but then once downloaded, we want developers to not have to worry about committing them ever. This feels like a very reasonable and common use case, and one for which "hidden_changes.conf" is made for.

   However, when we switch branches/changelist (which is very often!), we get the following error-looking dialog for any files we are locally changing but that ARE in "hidden_changes.conf" (see image).

   Ideally, if a file is in "hidden_changes" it wouldn't cause such an error and not put up any dialog. (e.g. I know it's a different use case but files that are cloaked don't put up a dialog) If there are any concerns about communication at the very least it should be a more friendly dialog such as "the following files are marked as HIDDEN CHANGES and have been changed and will NOT be updated to the new change list".

   Some configuration files & libraries etc. can need to be present, but customized/recompiled per-developer.

   We want to commit them to the repository (as they DO need to be present in at least a "default" state), but then once downloaded, we want developers to not have to worry about committing them ever. This feels like a very reasonable and common use case, and one for which "hidden_changes.conf" is made for.

   However, when we switch branches/changelist (which is very often!), we get the following error-looking dialog for any files we are locally changing but that ARE in "hidden_changes.conf" (see image).

   Ideally, if… more

   •  

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. 1D history

   I often need to look up the history of a file, but I only care about its changes on the /main branch. From the regular history view, when the file got changed on a branch, it is unclear whether that branch made it back to /main or not. The current history view is fairly pointless because there is no way to tell which changes are relevant and which ones have been abandoned.

   The 2D history view on the other hand is way too cluttered and cumbersome to navigate for any non-trivial project. Especially as it includes changesets where the file was merge from /main to another branch, which is exactly the opposite of what I want to know.

   What I really want is a way to filter the regular history view to a single branch, but show all changeset affecting the file, including merges. The table format is good, I just need a way to filter out all the irrelevant changes that never made it back to /main.

   I often need to look up the history of a file, but I only care about its changes on the /main branch. From the regular history view, when the file got changed on a branch, it is unclear whether that branch made it back to /main or not. The current history view is fairly pointless because there is no way to tell which changes are relevant and which ones have been abandoned.

   The 2D history view on the other hand is way too cluttered and cumbersome to navigate for any non-trivial project. Especially as it includes changesets where the file… more

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Gitsync files processing log

   Having a live log of gitsync processing files (not just the ring/percentage, and steps).
   There's many occasions on which it stays for 10, 20 minutes on the same % and it's hard to know if it's not working or simply processing more or less files.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Pending changes checkboxes need to be half filled if you haven't selected every child item

   •  

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Open file in file system

   When I view file changes in the Compare Revisions window, I often want to know the current state of the file or change it. Add an option to locate the file in local workspace if it exists locally. It's not the same as current option to open that revision in a temp. directory.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Revert a changeset option in context menu

   In Git UI I used to be able to do a simple task of reverting a selected commit locally. I saw an option to delete a changeset in Plastic, but sometimes you don't have a permission but you need to revert all the changes without opening any Diff windows and selecting any individual files.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Add an option to not merge formatting automatically

    I could not find an option to merge files manually when source has formatting and whitespace changes. These changes are lost after an auto-merge.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Default ignore settings for Unity projects

    When starting a new project, allow the user to indicate that it is a Unity project, and enact default ignore file settings based on best practices. Allow the user to see which files will be ignored, and override them.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Add C++17 support to SemanticMerge

    SemanticMerge doesn't understand e.g. nested namespace definitions, which means it can't semantically merge C++17 files.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Provide Branch information in Conflict Resolution Dialog

    Update the Conflict Resolution dialog to include additional information about the conflict.

    In particular, it would be helpful during a branch merge to know which branch is being considered as the Source and which is the Destination.

    In the attached example, it would be helpful to know that the Delete operation occurred on the /develop branch, and the change operation occurred on the /develop/tileeffectsupdate child branch.

    This will further clarify and confusion about which action to perform.

    •  

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Maintain/Display the change comments for Rename function

    Hi,
    We've recently had to rename a bunch of our files, and we were applying comments at check-in (because it was required), but have noticed that after the Check-In, the History will show the Move action, but no longer display the comment attached.

    This would have been useful for us, as the comments kept track of some important information around why the renaming was happening, but this info is either lost/not displayed.

    Cheers.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Improve merge changes context menu descriptions

    It would be nice if the context menu descriptions when resolving a merge conflict would be more informative.

    I'm referring to "Merge keeping source changes" and "Merge keeping workspace changes". The user has to know exactly which one is which, making this very error-prone.

    I suggest using "mine" and "theirs", as is common in other tools, or if possible, the name of the branch of each version.

    So "Merge keeping changes from 'main'" and "Merge keeping changes from 'main/fix-163'" would be much more informative.

    •  

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Autofill & Disable "Server" field when "Use relative server" is checked in XLink dialogue

    When I am in a workspace that is linked to SomeRepo@SomeCompany@cloud, and I create a new XLink, the XLink dialogue by default has Target Server set to local, and Use Relative Server set to true. These are incompatible! Either relative shouldn't be checked by default, or the server default should match the workspace's server. I think the latter option is more convenient for most use cases.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. experimental checkin feature for gluon

    I hear from my designer-y people that they'd like to be able to experiment with features before checking them in to the cloud. Naturally this can be done with branches with the regular plastic, but I'd like for them to keep utilizing the simplicity of gluon.

    I don't have a solid suggestion as to how to implement this, but as an alternative to checkin you could provide a "experimental checkin" action. Gluon still behaves as normal, but these checkins are only present for the user. When the user is done experimenting, they can checkin their experimental changesets to the cloud or abandon them alltogether.

    Like I said I don't know if this is feasible, but it would be a handy tool for the linear workflow gluon provides!

    I hear from my designer-y people that they'd like to be able to experiment with features before checking them in to the cloud. Naturally this can be done with branches with the regular plastic, but I'd like for them to keep utilizing the simplicity of gluon.

    I don't have a solid suggestion as to how to implement this, but as an alternative to checkin you could provide a "experimental checkin" action. Gluon still behaves as normal, but these checkins are only present for the user. When the user is done experimenting, they can checkin their experimental changesets to the cloud… more

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Marked branch always visible

    "Marked" branches should always be visible, even when they don't have any new changesets in the last couple of days/weeks so that I don't have to scroll back for a merge.

    This could be achieved by sticking the last changeset of a "marked" branch to the left edge of the branch explorer

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Check out from "Checkin changes" tab (Gluon)

    If you have a file in your Checkin changes tab that is Changed but not checked out, you currently have to switch to the Explore workspace tab and navigate to the file, then check it out.

    I would like to be able to bring up the context menu for the file under the Checkin changes tab and choose Check out.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Programatically Access Code Review Comments

    I am aware of PLASTICREVIEWCOMMENT and PLASTICREVIEWCOMMENT_ACTION events which seem handy for people who self-host. For us cloud-based folks, though, I don't believe there is any ability to even set up webhooks against these events.

    Right now all my devops scripts for tracking code review (mostly to publish changes to our team's discord) make use of 'cm find review ...'. However, I can't figure out any way to access the actual comments associated with a review so the only useful changes I can track are changes in status and assignee.

    Could you please add a feature to cm find that tracks code review comments, using the code review id as a foreign key? Then I could at least parse the output of something like cm find review_comment where review_id = 5555555 to determine if new comments can be added and publish those to our team's discord. Or if there is some existing way to accomplish this without using triggers, could you please let me know? (or if there are any plans to actually make triggers available to cloud users, via webhooks or whatever)

    Thanks

    I am aware of PLASTICREVIEWCOMMENT and PLASTICREVIEWCOMMENT_ACTION events which seem handy for people who self-host. For us cloud-based folks, though, I don't believe there is any ability to even set up webhooks against these events.

    Right now all my devops scripts for tracking code review (mostly to publish changes to our team's discord) make use of 'cm find review ...'. However, I can't figure out any way to access the actual comments associated with a review so the only useful changes I can track are changes in status and assignee.

    Could you please add a feature… more

    9 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close