Jump to content

Search the Community

Showing results for tags 'code review'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Plastic SCM on Mac
    • Plastic SCM on Linux
    • Gluon
    • Git interop
    • Integrations
    • Community Edition
    • Branching and merging
    • Announcements
  • Plastic SCM 4.0 Beta (Closed)
  • Plastic Cloud
    • General
    • Configuration
  • SemanticMerge
    • General
    • License
    • SCM's configuration
    • Share your experience!
    • External Parsers
  • GitJungle
  • Method History for Subversion

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 13 results

  1. Hi, I wonder if it is possible to create a Uniform Resource Identifier (URI) to a Code Review within Plastic desktop application? My use case is that I want to be able to send code review links to my coworkers so that they can trivially locate the code review. For instance: When a user opens a URI link to a Code Review, the desktop application of Plastic SCM should open and show the Code Review as if the user manually navigated in the GUI to find the Code Review and finally opening it via double-cliking the Code Review from within the Code reviews-tab. So I am looking for someth
  2. We've just started using plasticSCM for unity development with two developers and so far are generally loving it! we've run into an issue where I would make a comment on a code review, push the branch, then get a reply on that question that resolves the issue so after pulling again to see the reply, I want to delete original question, but after I delete it and push the branch, it does not get replciated on the other developers machine. the comment is still there after being deleted? is there any help someone can provide? maybe we've setup something wrong I'm not sure
  3. Hey all, Been building a fun little tool to keep our small dev team apprised of code review events in on our discord server. Currently it's able to identify newly created code reviews, changes in status and changes in assignee. The one remaining function I'd really like to add is the addition of code review comments, but I cannot find any way to access these outside the full PlasticSCM GUI. Pretty much all the other functionality works using cm find review where ... Nothing in the "cm find" documentation suggests that looking up review comments is possible, but I'm wondering if anyone
  4. Hello. Is there an option to create / perform code a code review on Plastic on Linux as there is on Windows?
  5. When using the new WebUI, the code review doesn't have a word wrap feature, nor does it have a horizontal scroll bar. If it goes off the screen, the only way to be able to see it all is to expand the browser window across multiple monitors, or shrink the zoom significantly. Also, it appears that when our users insert comments - only the comments on the first files are remembered. Anything after gets lost. Is there anywhere in the config files that I can make a change to fix this?
  6. When a file is added to the repository, I can't seem to add comments to the file, only view the file. The pane below says "To add a new comment, ..." and gives directions but they don't seem to work. Is this a bug in the code review system or did I miss something?
  7. We currently use plastic in a distributed setup with local servers (pulling/pushing from each other), with a master server to manage continuous integration. We wanted to try and use the code review feature of plastic, thinking it worked similar to a pull request in git, but this does not seem to be the case. If a developer has completed his work, and creates a code review for it. I have no idea the work is done because that review does not show up in my plastic client. Can someone explain how code reviews can or should be used in a distributed environment. Right now, when a
  8. Hi! We have just noticed that it is impossible to add comments to a code review that only has added files. You can reproduce it easily: Create a branch, check in a new file to the branch, create a CR for the branch, open the CR and you won't be able to comment. Modify another, but existing file in the same branch and check it in, open the same CR (where you will have now an added and a changed file), you will notice that commenting is now possible. Could you please fix that? We noticed it in, but I'm sure the bug was introduced earl
  9. I can't find the code review features in the linux client. Is there anything to do to enable it or is it missing ? If it's missing, where can I get a list of the missing features present in the Windows client but not on Linux or Mac ? Thanks, Fabien
  10. Hi there! :-) I've just talked to my colleague that performs code reviews for us. He has recently updated Plastic SCM to the release that has the new diff GUI ( - Kansas). It seems that there are a few things he misses very much in the code reviews window. Let me start from the most important one. In older Plastic SCM releases it was possible to move to the next/previous file using keyboar shortcuts. This feature was removed, and the only available shortcuts are those for navigation through changes in the diff pane. While verifying changes, he could previously navigate throug
  11. We have been using the Plastic inbuilt code review system for months. This system is very basic and has not many features, however we have improved it in some ways by integrating it with our other tools using attributes, triggers and other utilities. Though, there are still a few things which can help us to use it more effectively. Here are our suggestions: The ordering of comments in code review is not very practical and it doesn't encourage discussion. Some solutions (including a really simple one – just change the sorting algorithm) are already added as a UserVoice suggestion and it ha
  12. Hi All, Newbie here so please forgive me if this question has been asked before or I am just missing something simple. Anyway, I have 2 questions : 1. Are triggers associated with individual repositories or the server as a whole? The reason I ask is that I have several repositories but currently want a trigger to only affect one of them. 2. I want to create a code review whenever a change set is checked in. Can anyone tell me what I need to do trigger-wise to make this happen. Thank you
  13. Hi guys, i've got another idea. It's kind of simple but effective. Could you add a number behind the code review menu item which shows the user how many code reviews are assigned to him? Maybe it could even flash up a bit when there are new reviews. Kind regards, BB
  • Create New...