You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, many projects put more labeling / tagging effort into their issues rather than the pull requests that close them. For example, a PR might have no labels itself, but might close an issue labeled documentation.
Proposal
If a Pull Request doesn't contain any information that can be used to categorize it, but it does have an issue that it closes, then we should try to infer the "category" of the PR by looking at the issue's information.
Note on implementation
We can grab the pointer to a closing issue via the closingIssuesReferences graphql field. We can then use this to return the title and list of labels for that issue. Here's a rough query that does this for a generic pull requests query:
Context
We currently check for tags or metadata in titles for the pull request that was merged within a given window:
github-activity/github_activity/github_activity.py
Lines 471 to 484 in 2851438
However, many projects put more labeling / tagging effort into their issues rather than the pull requests that close them. For example, a PR might have no labels itself, but might close an issue labeled
documentation
.Proposal
If a Pull Request doesn't contain any information that can be used to categorize it, but it does have an issue that it closes, then we should try to infer the "category" of the PR by looking at the issue's information.
Note on implementation
We can grab the pointer to a closing issue via the
closingIssuesReferences
graphql field. We can then use this to return the title and list of labels for that issue. Here's a rough query that does this for a generic pull requests query:Tasks and updates
No response
The text was updated successfully, but these errors were encountered: