Skip to content

chore(pm): close items delivered by merged pull requests - #32

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
pm-github/closeout
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
pm-github/closeout

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Automated pm-github merged-PR closeout for unbraind/pm-ado.

The closeout command verified merged-PR delivery and head checks. The proposed tracker change and regenerated changelog passed the fail-closed privacy gate before anything was committed. main is never pushed directly.

Tracker items changed:

Closeout plan (routine skips counted by reason):

{
  "plan": [
    {
      "item": "pm-ado-g4v1",
      "pr": 11,
      "action": "refuse",
      "code": "epic"
    },
    {
      "item": "pm-ado-ns93",
      "pr": 15,
      "action": "close",
      "code": "head_checks_passed"
    },
    {
      "item": "pm-ado-g4v1",
      "pr": 15,
      "action": "refuse",
      "code": "epic"
    },
    {
      "item": "pm-ado-qq1p",
      "pr": 16,
      "action": "close",
      "code": "head_checks_passed"
    },
    {
      "item": "pm-ado-5w3m",
      "pr": 16,
      "action": "close",
      "code": "head_checks_passed"
    },
    {
      "item": "pm-ado-fiw8",
      "pr": 25,
      "action": "close",
      "code": "head_checks_passed"
    },
    {
      "item": "pm-ado-nc7z",
      "pr": 29,
      "action": "close",
      "code": "head_checks_passed"
    },
    {
      "item": "pm-ado-m8c1",
      "pr": 31,
      "action": "close",
      "code": "head_checks_passed"
    },
    {
      "item": "pm-ado-github-5532dc4b9a65-33",
      "pr": 35,
      "action": "refuse",
      "code": "not_delivery"
    }
  ],
  "skipped": {
    "already_terminal": 22,
    "duplicate_selection": 2,
    "other_repository": 122
  }
}

Summary by Sourcery

Close tracker items delivered by verified merged pull requests and synchronize the changelog with the completed work.

Bug Fixes:

  • Close six delivered tracker items after verifying their merged pull requests and delivery head checks.
  • Record completed closeout events in the corresponding tracker histories.

Enhancements:

  • Update the changelog with the delivered Azure DevOps, GitHub sync, dependency certification, and coverage-threshold work.

Chores:

  • Regenerate tracker metadata for the six items closed by the automated merged-pull-request closeout.

@greptile-apps

greptile-apps Bot commented Oct 17, 2026

Copy link
Copy Markdown

PR author is in the excluded authors list.

@sourcery-ai

sourcery-ai Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This automated closeout updates six tracker items only after merged-PR delivery and head checks passed, appends auditable history records, and regenerates the changelog; epic items and routine skips remain explicitly excluded, with changes gated before commit and no direct push to main.

Sequence diagram for gated merged-PR tracker closeout

sequenceDiagram
    participant Closeout as pm-github closeout
    participant GitHub
    participant Gate as Privacy gate
    participant Tracker as Tracker files
    participant History as History records
    participant Changelog
    participant PR as Closeout PR
    Closeout->>GitHub: verify merged-PR delivery
    Closeout->>GitHub: verify head checks
    alt head_checks_passed
        Closeout->>Tracker: close tracker item
        Closeout->>History: append closeout record
    else epic
        Closeout-->>Tracker: refuse item
    end
    Closeout->>Changelog: regenerate changelog
    Closeout->>Gate: validate tracker and changelog changes
    Gate-->>Closeout: pass or fail closed
    Closeout->>PR: commit and propose gated changes
    PR-->>GitHub: merge through pull request
Loading

Flow diagram for merged-PR closeout decisions

flowchart TD
    A[Select merged PR item] --> B{Delivery and head checks pass?}
    B -->|Yes| C[Close tracker item]
    B -->|No: epic| D[Refuse item]
    C --> E[Append history record]
    D --> F[Count routine skip]
    E --> G[Regenerate changelog]
    G --> H{Privacy gate passes?}
    H -->|Yes| I[Create closeout PR]
    H -->|No| J[Fail closed before commit]
    F --> K[Keep main unchanged]
    I --> K
Loading

File-Level Changes

Change Details Files
Close six delivered tracker items and record their terminal history after merged-PR and head checks passed.
  • Transitioned the six selected work items to closed state.
  • Appended one history event for each closeout.
  • Preserved refusal of epic items and reported routine skips by reason.
.agents/pm/chores/pm-ado-fiw8.toon
.agents/pm/chores/pm-ado-m8c1.toon
.agents/pm/chores/pm-ado-qq1p.toon
.agents/pm/features/pm-ado-nc7z.toon
.agents/pm/issues/pm-ado-5w3m.toon
.agents/pm/issues/pm-ado-ns93.toon
.agents/pm/history/pm-ado-5w3m.jsonl
.agents/pm/history/pm-ado-fiw8.jsonl
.agents/pm/history/pm-ado-m8c1.jsonl
.agents/pm/history/pm-ado-nc7z.jsonl
.agents/pm/history/pm-ado-ns93.jsonl
.agents/pm/history/pm-ado-qq1p.jsonl
Regenerate the changelog to document the delivered features, fixes, and dependency/tooling updates.
  • Added entries for Azure DevOps relation validation and import/export reconciliation.
  • Recorded pm-github gated sync/closeout and GitHub issue sync changes.
  • Documented coverage enforcement and PM CLI/SDK certification updates.
CHANGELOG.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 11600d5e-7a4a-4b0e-84fd-3d8eab7b1e80

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 1 issue

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="CHANGELOG.md" line_range="12" />
<code_context>

 ### Added

+- Import, export and reconcile Azure DevOps work items with revision-checked commands ([pm-ado-nc7z](https://github.com/unbraind/pm-ado/blob/main/.agents/pm/features/pm-ado-nc7z.toon))
 - Map typed work item relations onto pm parent and dependency kinds in both directions ([pm-ado-1zuu](https://github.com/unbraind/pm-ado/blob/main/.agents/pm/features/pm-ado-1zuu.toon))
 - Read a project through the work item batch endpoint instead of one request per item ([pm-ado-ntkc](https://github.com/unbraind/pm-ado/blob/main/.agents/pm/features/pm-ado-ntkc.toon))
</code_context>
<issue_to_address>
**October work appears in September release**

When closeout regeneration adds work merged after the 2026-09-02 release while `package.json` still sets version `2026.9.2`, `changelog:full` renders the Azure DevOps sync under the existing `2026.9.2 - 2026-09-02` heading, attributing October delivery to a September release that does not contain it.

Update the release version and add a new dated changelog section before listing post-release work.

Also at `CHANGELOG.md:13`.
</issue_to_address>

Sourcery assessment

Needs a human reviewer. 1 finding to address first, and if an item is closed incorrectly, its status and close evidence remain in the tracker files, and the changelog may list work under the wrong category; those records can be corrected with a follow-up change. The diff shows no external tracker write or irreversible action.

Blocking findings: CHANGELOG.md:12


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread CHANGELOG.md

### Added

- Import, export and reconcile Azure DevOps work items with revision-checked commands ([pm-ado-nc7z](https://github.com/unbraind/pm-ado/blob/main/.agents/pm/features/pm-ado-nc7z.toon))

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Medium · October work appears in September release

When closeout regeneration adds work merged after the 2026-09-02 release while package.json still sets version 2026.9.2, changelog:full renders the Azure DevOps sync under the existing 2026.9.2 - 2026-09-02 heading, attributing October delivery to a September release that does not contain it.

Update the release version and add a new dated changelog section before listing post-release work.

Also at CHANGELOG.md:13.

Prompt for AI agents
In `CHANGELOG.md` at line 12:

**October work appears in September release**

When closeout regeneration adds work merged after the 2026-09-02 release while `package.json` still sets version `2026.9.2`, `changelog:full` renders the Azure DevOps sync under the existing `2026.9.2 - 2026-09-02` heading, attributing October delivery to a September release that does not contain it.

Update the release version and add a new dated changelog section before listing post-release work.

Also at `CHANGELOG.md:13`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants