Skip to content

fix(DDUw): recognize non-[docs] PR closures in step 1c to avoid redundant re-scanning #26443

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

Merged
pelikhan merged 2 commits into from
Apr 15, 2026
+1 −1
Merged

fix(DDUw): recognize non-[docs] PR closures in step 1c to avoid redundant re-scanning #26443

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6e93b5d
Initial plan
Copilot Apr 15, 2026
5a0e95a
fix: recognize non-[docs] PR closures in DDUw step 1c to avoid redund…
Copilot Apr 15, 2026
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
2 changes: 1 addition & 1 deletion .github/workflows/daily-doc-updater.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ repo:${{ github.repository }} is:issue is:closed label:documentation closed:>=YY
```

For each closed issue:
- **closed as completed**: Check whether a `[docs]` PR references it. If no such PR exists, treat it as an unaddressed gap and follow the normal Step 2 flow.
- **closed as completed**: Check whether a `[docs]` PR references it. If no such PR exists, also search for any merged PR that closes or fixes the issue by number (e.g. `closes #NNN`, `fixes #NNN`, `resolves #NNN` in the PR body). If such a PR is found and its documentation change is complete, skip the issue. Otherwise, treat it as an unaddressed gap and follow the normal Step 2 flow.
- **closed as not_planned**: Do not create documentation based solely on this issue. Instead, cross-reference the issue's subject matter against commits from the same 7-day window (Step 2). If a related code change is found, treat it as a new documentation gap (independent of the original issue decision) and follow the normal Step 2 flow for that code change.

### 1d. Scan Cookie-Labeled Automation Issues
Expand Down
Loading