[ARROW-18377] MIGRATION: Automate component labels from issue form content

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 11.0.0
• Component/s: Continuous Integration, Developer Tools
• Labels: gh-migration pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/33543
• Assignee: Jacob Wujciak
• Reporter: Todd Farmer
• Created: 21/Nov/22 21:11
• Updated: 11/Jan/23 11:59
• Resolved: 08/Jan/23 17:27

Description

ARROW-18364 added the ability to report issues in GitHub, and includes GitHub issue templates with a drop-down component(s) selector. These form elements drive resulting issue markdown only, and cannot dynamically drive issue labels. This requires GitHub actions, which also have a few limitations. First, the issue form does not produce any structured data, it only produces the issue description markdown, so a parser is required. Second, ASF restricts GitHub actions to a selection of approved actions. It is likely that while community actions exist to generate structured data from issue forms, the Apache Arrow project will need to write its own parser and label application action.

Issue Links

• links to: GitHub Pull Request #15245