Jump to content

Search the Community

Showing results for tags 'attributes'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Unreal Engine
    • 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
  • PlasticX Early Adopter Program's General Feedback
  • PlasticX Early Adopter Program's Issue Reporting
  • PlasticX Early Adopter Program's Feature Requests
  • PlasticX Early Adopter Program's Announcements

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. Are proper cloud triggers still not supported? I want to set up adding attributes to branches on creation per this article https://blog.plasticscm.com/2019/06/archive-branches-in-plastic-scm.html
  2. Hello, Is it possible to add an "Attributes" column on the "Branches" screen? See attached screenshot.
  3. In the CLI, is there a way to display what custom attributes are assigned to a branch object, and what their values are? I can use "cm find" to locate a particular branch, but there doesn't appear to be any output options on the command to list the attributes or values set on that branch. The --format option does not include attributes as possible output. The --xml option looks like it could handle attributes, but does not list them. Is there a way? Or should this be a feature request?
  4. In order to filter out branches that have been merged and/or abandoned (like test branches), I was looking into attributes as they seemed like the easiest way to have a blanket identifier for this kind of flag. I am able to easily add a "find branches where attribute='Closed' " to find the closed branches, but how can I do the inverse of this? I would like to have a filter that shows everything with an attribute != 'Closed". I know I could add an attribute to everything, mark it as "1" and set "0" as the "hide" options, but that requires every branch to be updated and modified. Only on finished code reviews should an attribute be appended in order to keep the workflow easy. Does anyone have any knowledge about Query statement logic and syntax? The documentation only shows "=" examples. Thank you!
×
×
  • Create New...