assignUser commented on issue #14720: URL: https://github.com/apache/arrow/issues/14720#issuecomment-1325528178
1. ` GitHub issues: GH-XXXXX` :heavy_multiplication_x: :heavy_multiplication_x: The link between issue and PR should be made with the intended GH functionality, so either using a keyword like "closes #123" or manually linking the PR and issue via the web gui. Adding the keyword to the PR body is basically the same as the `ARROW-123` in the title, so replacing one with the other should be fine. 2. We already have the labeler workflow that could easily be adapted to label components by the sub dirs of the changed files (e.g. r/* -> R cpp/* -> C++ dev/archery/* -> Developer dev/tasks -> CI ...) 3. :+1: 4. For issues it would make sense to assign them when you start working on them. We could have the bot add the PR creator as an assignee on the matching issue on opening the PR. That would keep things consistent and also mark the issues as WIP? I don't think we need to use the assignee field on PRs themselves though. I am unsure on the details of parquet as a "sub-project"(?) but I really don't think it makes any sense to use two separate tools for issue tracking within the same repo. -- 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]
