Search before asking
Use case
No response
Description
GitHub is introducing GitHub Issue Fields. This seems to be in line with the data that DevLake already syncs, so I imagine it's something that a lot of people would want.
For my use case, we are currently using type labels: https://www.notion.so/mui-org/GitHub-labels-af1ef18d3f534f1dbc086aac87b819e8?source=copy_link#266cbfe7b66080189135c731bc25e67f, but those:
- Are not mutually exclusive, we shouldn't be able to apply
type: bug and type: regression at the same time
- Are not shared across the GitHub organizations (labels are repo-based)
So we will migrate to them as soon as it's good enough in GitHub. But we don't want reports like those: https://www.notion.so/mui-org/Pull-request-types-1abcbfe7b66080f4a5a6e593e0a90ce4?source=copy_link#1c6cbfe7b66080158cddc675bbb948ca
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Search before asking
Use case
No response
Description
GitHub is introducing GitHub Issue Fields. This seems to be in line with the data that DevLake already syncs, so I imagine it's something that a lot of people would want.
For my use case, we are currently using type labels: https://www.notion.so/mui-org/GitHub-labels-af1ef18d3f534f1dbc086aac87b819e8?source=copy_link#266cbfe7b66080189135c731bc25e67f, but those:
type: bugandtype: regressionat the same timeSo we will migrate to them as soon as it's good enough in GitHub. But we don't want reports like those: https://www.notion.so/mui-org/Pull-request-types-1abcbfe7b66080f4a5a6e593e0a90ce4?source=copy_link#1c6cbfe7b66080158cddc675bbb948ca
Related issues
No response
Are you willing to submit a PR?
Code of Conduct