Widen doc-updater scan window to 3 weeks - #18
Merged
Conversation
Change the daily-doc-updater agentic workflow to look back 3 weeks instead of the last 24 hours when scanning ohcnetwork/care for merged PRs and commits to document. Body changes in daily-doc-updater.md: - Step 1 heading "Scan Recent Activity (Last 24 Hours)" -> "(Last 3 Weeks)". - Date calc: date -u -d "1 day ago" -> date -u -d "3 weeks ago" (GNU date on the ubuntu runner supports "3 weeks ago"); still feeds the merged:>=YYYY-MM-DD search filter. - All prose references to "last 24 hours" / "yesterday" updated to "last 3 weeks" (mission statement, Step 1 bullets, PR-description template, and the No recent changes edge case). Care-repo targeting from #17 and the pre_activation check throttle are left unchanged; frontmatter is untouched. Regenerated daily-doc-updater.lock.yml with gh aw compile (pinned v0.81.6): only body_hash changes; frontmatter_hash, compiler_version and engine version are unchanged. A second compile is a no-op. Co-authored-by: Copilot App <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Widens the
daily-doc-updateragentic workflow's scan window from the last 24 hours to the last 3 weeks when looking atohcnetwork/carefor merged PRs/commits to document..github/workflows/daily-doc-updater.md(body only — frontmatter untouched):date -u -d "1 day ago" +%Y-%m-%d→date -u -d "3 weeks ago" +%Y-%m-%d(GNU date on the ubuntu runner supports"3 weeks ago"), still feeding themerged:>=YYYY-MM-DDsearch filter.search_pull_requests/list_commitsbullets, the PR-description template, and the No recent changes edge case. (Grepped the file for24 hours/1 day/yesterday— zero remaining.)ohcnetwork/caretargeting from Point doc-updater at ohcnetwork/care for change detection #17 and the pre_activationcheckthrottle are unchanged..github/workflows/daily-doc-updater.lock.ymlregenerated withgh aw compile(extension pinned to v0.81.6):body_hashchanges;frontmatter_hash,compiler_version(v0.81.6) and engine version (copilot 1.0.65) are unchanged.gh aw compileis a no-op (idempotent). The untracked.github/aw/actions-lock.jsonandagentics-maintenance.ymlare not committed.This workflow runs on a daily schedule (
schedule: dailyin the frontmatter), but now looks back 3 weeks. That means every day it re-scans the same ~3 weeks of mergedohcnetwork/carePRs — including ones it already documented on previous runs. There is no dedupe against already-documented changes, so the agent may open duplicate[docs]PRs for work that's already been covered.The existing
MAX_OPEN_PRS=8pre_activation throttle (gh pr list --repo "$GITHUB_REPOSITORY" ... in:title "[docs]") only caps the number of concurrently-open[docs]PRs — it does not deduplicate content, so you can still get repeated/overlapping doc PRs churning day to day until the cap is hit.Suggested follow-ups (out of scope for this PR — flagging for the maintainer):
[docs]PRs or already-documented PR numbers before creating a new one), and/or