Skip to content

feat: Add staleness check workflow for Platform docs - #3080

Open
szaganek wants to merge 4 commits into
masterfrom
feat/staleness-check
Open

szaganek wants to merge 4 commits into
masterfrom
feat/staleness-check

Conversation

@szaganek

@szaganek szaganek commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Adds a monthly workflow that checks for stale topics in sources/platform and creates an issue with a list of topics that haven't been touched in the last 6 months. Skips frontmatter-only changes, bulk commits that involve more than 10 .md/.mdx files, and commits listed in .staleness-check-ignore.

How a resulting issue looks like: #3081

Closes #3080

@szaganek szaganek self-assigned this Oct 15, 2026
@szaganek szaganek added the t-docs Issues owned by technical writing team. label Oct 15, 2026
@apify-service-account

apify-service-account commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

✅ Preview for this PR (commit e763cfb) is ready at https://pr-3080.preview.docs.apify.com (see action run).

@szaganek
szaganek requested review from TC-MO and marcel-rbro October 15, 2026 12:52

@marcel-rbro marcel-rbro left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The description says Closes #3080, which is this PR. Should it be Closes #3009?

const previous = commits[i + 1];
if (!previous) return true;
const body = pageBodyAt(sha, path);
return body === null || body !== pageBodyAt(previous.sha, previous.path);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This compares bodies with frontmatter stripped, so a commit that only bumps last_review (the plan from the Slack thread) won't count as an edit and the page gets flagged again next month. Should the script also read last_review from the current frontmatter and use it when it's newer than the last content edit?

This branch has not been deployed

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

Labels

t-docs Issues owned by technical writing team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants