feat(stack): add mergify stack list command

[jd]

Add a new command to display the current stack's commits and their
associated PRs. Shows PR status (open, draft, merged, no PR) with
color-coded output.

Supports --json flag for scripting and --trunk to specify target branch.

Co-Authored-By: Claude Opus 4.5 [email protected]

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 🤖 Continuous Integration

Wonderful, this rule succeeded.

• all of:
  • check-success=ci-gate

🟢 👀 Review Requirements

Wonderful, this rule succeeded.

• any of:
  • #approved-reviews-by>=2
  • author = dependabot[bot]
  • author = mergify-ci-bot
  • author = renovate[bot]

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 🔎 Reviews

Wonderful, this rule succeeded.

• #changes-requested-reviews-by = 0
• #review-requested = 0
• #review-threads-unresolved = 0

🟢 📕 PR description

Wonderful, this rule succeeded.

• body ~= (?ms:.{48,})

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for 025ec40.

🟢 All jobs passed!

But CI Insights is watching 👀

[Copilot]

Pull request overview

This PR adds a new mergify stack list command to display commits in the current stack along with their associated pull request status. The command shows PR state (open, draft, merged, or no PR) with color-coded output and supports JSON output for scripting workflows.

Changes:

• Implements core stack listing logic with PR status detection
• Adds comprehensive test coverage for various stack states and edge cases
• Integrates the new command into the CLI interface with --json and --trunk flags

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
mergify_cli/stack/list.py	Core implementation of stack listing functionality with status detection and display formatting
mergify_cli/tests/stack/test_list.py	Comprehensive test suite covering PR states, JSON output, empty stacks, and error cases
mergify_cli/stack/cli.py	CLI integration adding the new list command with trunk and JSON output options

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default) at 025ec40

This pull request spent 1 minute 35 seconds in the queue, including 1 minute 19 seconds running CI.
The checks were run on draft #938.

Required conditions to merge

• all of [🛡 Merge Protections rule 🤖 Continuous Integration]:
  • all of:
    • check-success=ci-gate
• all of [🛡 Merge Protections rule Enforce conventional commit]:
  • title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:
    • feat(stack): add mergify stack list command #931
• all of [🛡 Merge Protections rule 👀 Review Requirements]:
  • any of:
    • #approved-reviews-by>=2
      • feat(stack): add mergify stack list command #931
    • author = dependabot[bot]
      • feat(stack): add mergify stack list command #931
    • author = mergify-ci-bot
      • feat(stack): add mergify stack list command #931
    • author = renovate[bot]
      • feat(stack): add mergify stack list command #931
• all of [🛡 Merge Protections rule 📕 PR description]:
  • body ~= (?ms:.{48,})
    • feat(stack): add mergify stack list command #931
• all of [🛡 Merge Protections rule 🔎 Reviews]:
  • #changes-requested-reviews-by = 0
    • feat(stack): add mergify stack list command #931
  • #review-requested = 0
    • feat(stack): add mergify stack list command #931
  • #review-threads-unresolved = 0
    • feat(stack): add mergify stack list command #931

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• ❌ ci-gate

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[jd]

@Mergifyio requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[mergify]

Merge Queue Status

✅ The pull request has been merged at 025ec40

This pull request spent 2 minutes 6 seconds in the queue, including 1 minute 51 seconds running CI.
The checks were run on draft #939.

Required conditions to merge

• all of [🛡 Merge Protections rule Enforce conventional commit]:
  • title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:
    • feat(stack): add mergify stack list command #931
• all of [🛡 Merge Protections rule 👀 Review Requirements]:
  • any of:
    • #approved-reviews-by>=2
      • feat(stack): add mergify stack list command #931
    • author = dependabot[bot]
      • feat(stack): add mergify stack list command #931
    • author = mergify-ci-bot
      • feat(stack): add mergify stack list command #931
    • author = renovate[bot]
      • feat(stack): add mergify stack list command #931
• all of [🛡 Merge Protections rule 📕 PR description]:
  • body ~= (?ms:.{48,})
    • feat(stack): add mergify stack list command #931
• all of [🛡 Merge Protections rule 🔎 Reviews]:
  • #changes-requested-reviews-by = 0
    • feat(stack): add mergify stack list command #931
  • #review-requested = 0
    • feat(stack): add mergify stack list command #931
  • #review-threads-unresolved = 0
    • feat(stack): add mergify stack list command #931
• all of [🛡 Merge Protections rule 🤖 Continuous Integration]:
  • all of:
    • check-success=ci-gate