Skip to content

fix: eliminate cache-memory dependency in update-instructions workflow #8739

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vhvb1989 wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −13
Open

fix: eliminate cache-memory dependency in update-instructions workflow #8739

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 8 additions & 13 deletions .github/workflows/update-instructions-from-pr-reviews.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,7 @@ permissions:
copilot-requests: write
pull-requests: read
issues: read
actions: read

engine: copilot

Expand All @@ -64,9 +65,6 @@ tools:
toolsets: [pull_requests, issues, repos]
# Lets the agent read and edit the local .github/ customization files.
edit:
# Remembers the last successful run date so "since last run" works with no
# external state. The agent reads/writes a small marker here each run.
cache-memory:

safe-outputs:
create-pull-request:
Expand Down Expand Up @@ -154,11 +152,13 @@ Decide which merged PRs to examine, in this order of preference:

1. If the **Since** run parameter above is a real date (not `not set`), mine
PRs merged on/after that date.
2. Otherwise, read the **cache memory** for a marker file named
`last-run.txt`. If it exists, mine PRs merged after that timestamp ("since
last run").
3. Otherwise (first ever run, no marker), mine PRs merged within the last 6
months, capped at the **Max PRs** run parameter.
2. Otherwise, use the GitHub tools to list recent workflow runs for **this
workflow** (`Update Instructions From PR Reviews`) in the repository this
workflow runs in. Find the most recent **successful** (completed with
`conclusion: success`) run and use its `updated_at` timestamp as the
starting point — mine PRs merged after that date.
3. Otherwise (no previous successful run found), mine PRs merged within the
last 6 months, capped at the **Max PRs** run parameter.

The **Source repository** run parameter above already resolves to the repository
this workflow runs in when no override was supplied, so mine PRs from whatever
Expand Down Expand Up @@ -280,11 +280,6 @@ link to the pushed branch, so the proposed edits are never lost and Copilot can
open the PR from there. You don't need to do anything special — write the body
the same way; it's reused for the fallback issue.

## 8. Record the run

Write the current date (the high-water mark of mined PRs) to `last-run.txt` in
**cache memory** so the next scheduled run only processes newer PRs.

## Guardrails

- Never commit or push directly — all changes flow through the safe output.
Expand Down