You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by GitBox <gi...@apache.org> on 2022/08/14 02:58:57 UTC

[GitHub] [incubator-devlake] Startrekzky commented on issue #2469: how to config github, how to the the input

Startrekzky commented on issue #2469:
URL: https://github.com/apache/incubator-devlake/issues/2469#issuecomment-1214273945

   Hi @matthewxuda , the configuration rules are listed below:
   
   ### Issue Tracking
   Severity: Parse the value of severity from issue labels.
   
   - when your issue labels for severity level are like 'severity/p0', 'severity/p1', 'severity/p2', then input 'severity/(.*)$'
   - when your issue labels for severity level are like 'p0', 'p1', 'p2', then input '(p0|p1|p2)$'
   - Component: Same as "Severity".
   
   ### Priority: Same as "Severity".
   
   - Type/Requirement: The type of issues with labels that match given regular expression will be set to "REQUIREMENT". Unlike "PR.type", submatch does nothing, because for issue management analysis, users tend to focus on 3 kinds of types (Requirement/Bug/Incident), however, the concrete naming varies from repo to repo, time to time, so we decided to standardize them to help analysts metrics.
   
   - Type/Bug: Same as "Type/Requirement", with type setting to "BUG".
   
   - Type/Incident: Same as "Type/Requirement", with type setting to "INCIDENT".
   
   ### Code Review
   Type: The type of pull requests will be parsed from PR labels by given regular expression. For example:
   
   - when your labels for PR types are like 'type/feature-development', 'type/bug-fixing' and 'type/docs', please input 'type/(.*)$'
   - when your labels for PR types are like 'feature-development', 'bug-fixing' and 'docs', please input '(feature-development|bug-fixing|docs)$'
   - Component: The component of pull requests will be parsed from PR labels by given regular expression.
   
   ### Additional Settings (Optional)
   - Tags Limit: It'll compare the last N pairs of tags to get the "commit diff', "issue diff" between tags. N defaults to 10.
   
   - commit diff: new commits for a tag relative to the previous one
   issue diff: issues solved by the new commits for a tag relative to the previous one
   - Tags Pattern: Only tags that meet given regular expression will be counted.
   
   - Tags Order: Only "reverse semver" order is supported for now.
   
   Please click Save to save the transformation rules for the repo. In the data scope list, click Next Step to continue configuring.
   
   ------------------------------------------------------------------
   
   Please read this [doc](https://devlake.apache.org/docs/UserManuals/ConfigUI/GitHub#step-3---adding-transformation-rules-optional) for more details.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@devlake.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org