[CI] Add GitHub Action to auto-close parent issues

[SmartManoj]

Related GitHub Issue

#2211

Description

Add GitHub Action to auto-close parent issues when all child issues are closed

Test

https://github.com/SmartManoj/Roo-Code/actions/runs/15063558027/job/42343266065

Type of Change

• 🐛 Bug Fix: Non-breaking change that fixes an issue.
• ✨ New Feature: Non-breaking change that adds functionality.
• 💥 Breaking Change: Fix or feature that would cause existing functionality to not work as expected.
• ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.
• 💅 Style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
• 📚 Documentation: Updates to documentation files.
• ⚙️ Build/CI: Changes to the build process or CI configuration.
• 🧹 Chore: Other changes that don't modify src or test files.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Code Quality:
  • My code adheres to the project's style guidelines.
  • There are no new linting errors or warnings (npm run lint).
  • All debug code (e.g., console.log) has been removed.
• Testing:
  • New and/or updated tests have been added to cover my changes.
  • All tests pass locally (npm test).
  • The application builds successfully with my changes.
• Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates.
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

Additional Notes

---

Important

Adds GitHub Action close-parent.yml to auto-close parent issues when all child issues are closed using GraphQL API.

• Behavior:
  • Adds close-parent.yml GitHub Action to auto-close parent issues when all child issues are closed.
  • Triggers on closed issue events.
  • Uses GraphQL API to check sub-issue status and close parent if all are closed.
• Implementation:
  • Retrieves issue and parent IDs using GraphQL queries.
  • Checks sub-issues' states and closes parent issue if all are closed.
  • Logs messages for no parent issue or if not all sub-issues are closed.

^{This description was created by for 265857a. You can customize this summary. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: d1c517a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

Consider adding set -e at the start of the run block to ensure the script exits immediately if a command fails. This would help avoid unpredictable behavior on API errors.

^{This comment was generated because it violated a code review rule: mrule_OR1S8PRRHcvbdFib.}

[ellipsis-dev]

It would be beneficial to add error handling for the gh api graphql calls. For example, verify that the response contains the expected data before proceeding, to handle API errors gracefully.

^{This comment was generated because it violated a code review rule: mrule_OR1S8PRRHcvbdFib.}

[daniel-lxs]

Hey @SmartManoj, thank you for the contribution!

We've shifted to a issue-first workflow. I'll be closing this issue temporarily but that doesn't mean there's something wrong with this PR.

Feel free to reopen this PR if you create an issue for it. I look forward to improving our Github actions with this!

[SmartManoj]

How about a workflow to auto create an issue if it is not there?