Startrekzky opened a new issue, #6128:
URL: https://github.com/apache/incubator-devlake/issues/6128

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Use case
   
   DevLake's team uses DevLake to track DORA, but we can't tell in which 
environment a GitHub run or job is executed. We use two conditions to trigger 
the same run and job to deploy, hence, the names of the runs/jobs are the same 
for a `testing` deployment or `production` deployment.
   
   However, we can tell the environment by the ref name (branch name) in the 
screenshot. That's why I think the scope config should support the use case by 
adding branch_name into the scope of the env regex.
   
   
![image](https://github.com/apache/incubator-devlake/assets/14050754/e502f595-2333-4d03-8c83-85436516a6b6)
   
   
   ### Description
   
   The configuration for GitHub's Scope Config should be updated to:
   
   
![image](https://github.com/apache/incubator-devlake/assets/14050754/22f9d2f8-2e55-4c5b-b78e-b80ad00b5077)
   
   I use the branch name other than ref name for better understanding.
   
   There will be a few cases:
   1. GitHub workflow run's name matches the env regex: 
cicd_pipelines.environment will be `PRODCUTION`
   2. GitHub workflow run's ref_name matches the env regex: 
cicd_pipelines.environment will be `PRODCUTION`
   3. GitHub job run matches the env regex: cicd_tasks.environment will be 
`PRODCUTION`
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to