✨ feat(pipeline-proposals): add github action bot for tracking status

[kenibrewer]

This pull request introduces a new GitHub Actions workflow to automate the approval process for pipeline proposals. The workflow handles issue creation, comment-based voting, and status updates, ensuring that proposals are reviewed and approved or rejected based on team member input. It includes logic to manage labels, track votes, and update issue status dynamically.

New Workflow for Pipeline Proposal Approval:

• Workflow Setup: Added a new workflow file .github/workflows/pipeline_proposals.yml to automate the approval process for pipeline proposals triggered by issue events (opened, closed, labeled, unlabeled) and comments (created, edited).

• Approval Logic: Implemented logic to fetch team members, track approvals/rejections, and determine the proposal status based on voting rules (e.g., approvals required from either 2 core members or 1 core member + 1 maintainer).

• Dynamic Status Updates: Added functions to generate detailed status comments, format user lists, and update issue labels and states based on the current approval/rejection status.

• Timed-Out and Label Handling: Integrated label-based handling to mark proposals as "timed-out" and update the status accordingly.

[Copilot]

Pull Request Overview

This PR adds a GitHub Actions workflow to automate the approval process for pipeline proposals by tracking team votes and updating issue status and labels.

• Introduces a new workflow file that triggers on issue and comment events for "New Pipeline" issues.
• Implements functions to fetch core and maintainer team members and compute approval/rejection votes.
• Updates or creates status comments and adjusts issue labels and state based on voting rules and timeouts.

Comments suppressed due to low confidence (2)

.github/workflows/pipeline_proposals.yml:36

• [nitpick] The variable name res is generic. Renaming it to something more descriptive like response or teamMembersResponse will improve code clarity.

const res = await github.request('GET /orgs/{org}/teams/{team_slug}/members', {

.github/workflows/pipeline_proposals.yml:167

• The script reopens issues when they’re manually closed because it only closes in specific status cases. Consider adding an explicit guard to ignore manual closed events (those without state_reason set by the bot) before updating status to prevent unintentionally reopening issues.

if (context.eventName === 'issues' && context.payload.action === 'opened') {

[Copilot]

[nitpick] The inline script is 267 lines long, which can make maintenance difficult. Consider moving the logic into a separate JavaScript/TypeScript file in the repo and referencing it here to improve readability and reuse.

[ewels]

I couldn't agree more 👆🏻

Probably the same for the other one too actually. Is this possible to do with actions/github-script? Bonus points if we can have a shared utils.js to share functions..