chore: move draft PRs to in progress pipeline in ZenHub

[barjin]

Closes #92

[Copilot]

Pull Request Overview

Adds a GitHub Actions workflow that automatically moves issues linked from draft pull requests into the “In Progress” pipeline in ZenHub.

• Introduces a new workflow file triggering on various pull_request events
• Fetches closing issue references via GitHub CLI GraphQL
• Invokes zenhub-issue-manager to update each linked issue’s pipeline

Comments suppressed due to low confidence (3)

.github/workflows/update-draft-pr.yaml:32

• This condition only runs when draft == true, so the pipeline move won’t execute when a draft is marked ready for review (draft == false). Adjust the condition or event filter to trigger on the ready_for_review action or check for draft == false.

        if: github.event.pull_request.draft == true

.github/workflows/update-draft-pr.yaml:34

• Limiting the GraphQL query to the first 10 issues may omit additional linked issues. Consider increasing the limit or implementing pagination to ensure all references are processed.

          GITHUB_API_RESPONSE=$(gh api graphql -F query='query($owner: String!, $repoName: String!, $pr: Int!) { repository(owner: $owner, name: $repoName) { pullRequest(number: $pr) { closingIssuesReferences(first: 10) { nodes { number } } } } }' -F owner=${{ github.repository_owner }} -F repoName=${{ github.event.repository.name }} -F pr=${{ github.event.pull_request.number }} --jq '.data.repository')

.github/workflows/update-draft-pr.yaml:42

• [nitpick] Rather than using echo into GITHUB_ENV and then ${{ env.gh_api_response }}, consider capturing the response as a step output (via GITHUB_OUTPUT) or exporting a shell variable directly. This improves readability and scopes the data to the step.

          for issue in $(echo ${{ env.gh_api_response }} | jq -r '.pullRequest.closingIssuesReferences.nodes[].number'); do