dosubot[bot] commented on issue #7893:
URL:
https://github.com/apache/incubator-devlake/issues/7893#issuecomment-2287045425
<!-- Answer -->
To modify the configuration so that it records file names that were updated
during git commits and pull requests, you need to ensure that the data
collection includes the necessary entities related to commits and pull
requests. Specifically, you should ensure that the `Source Code Management` and
`Code Review` data entities are selected, as these will include information
about commits and pull requests.
Here is the relevant section from the configuration documentation that you
need to focus on:
```md
### Data Entities
Usually, you don't have to modify this part. However, if you don't want to
collect certain GitHub entities, you can unselect some entities to accelerate
the collection speed.
- Issue Tracking: GitHub issues, issue comments, issue labels, etc.
- Source Code Management: GitHub repos, refs, commits, etc.
- Code Review: GitHub PRs, PR comments and reviews, etc.
- CI/CD: GitHub Workflow runs, GitHub Workflow jobs, etc.
- Cross Domain: GitHub accounts, etc.
```
Ensure that `Source Code Management` and `Code Review` are selected to
collect data about commits and pull requests, which will include the file names
that were updated.
Additionally, you may need to configure the transformation rules to parse
the necessary information from the collected data. Here is how you can add
transformation rules:
```md
## Step 3 - Adding Transformation Rules (Optional)
Without adding transformation rules, you can still view the "[GitHub
Metrics](/livedemo/DataSources/GitHub)" dashboard. However, if you want to view
"[Weekly Bug Retro](/livedemo/EngineeringLeads/WeeklyBugRetro)", "[Weekly
Community Retro](/livedemo/OSSMaintainers/WeeklyCommunityRetro)" or other
pre-built dashboards, the following transformation rules, especially
"Type/Bug", should be added.
Each GitHub repo has at most ONE set of transformation rules.
### 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.
```
By ensuring the correct data entities are selected and configuring the
transformation rules, you can collect and record the file names that were
updated during git commits and pull requests
<sup>[[1]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.15/UserManuals/ConfigUI/GitHub.md)</sup><sup>[[2]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.17/Configuration/GitHub.md)</sup>.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
--
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: dev-unsubscr...@devlake.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
