Repository navigation
ci: open a data-due issue each Monday when records are due - #50
Merged
Merged
Conversation
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.
The weekly refresh no longer depends on remembering
pnpm data:report. Every Monday at 12:30 UTC (7:30 CDT, 6:30 CST) a workflow runs the report. When anything is due now or soon, it opens an issue labeleddata-duewith the list and closes last week's. A quiet week opens nothing.This does #39 differently from how it's written: an issue instead of a Discord post. The maintainer's own GitHub digest (Lain, in CozyCore) shows new issues in their Discord, so this repository holds no webhook or secret.
reportruns the repository's code withcontents: readand nothing else.issuehasissues: writeand never checks the code out. It reads the first job's outputs from environment variables and puts the report in a code block, so record names can't turn into Markdown.workflow_dispatchtakes an optional date, to see what a later Monday will bring. The CLI rejects anything that isn'tYYYY-MM-DD.docs/MAINTENANCE.mdandROADMAP.md(2026-10-20) describe it.I dry-ran both jobs locally, with a stand-in for
gh:The workflow hasn't run on GitHub yet. After merging, run it once from the Actions tab with no date (quiet), then with
2026-11-02(due).Closes #39