Skip to content

ci(weekly-lints): fail on a missing lint report and post a notice to Zulip - #886

Draft
jessealama wants to merge 1 commit into
leanprover:mainfrom
jessealama:ci/weekly-lints-guards
Draft

jessealama wants to merge 1 commit into
leanprover:mainfrom
jessealama:ci/weekly-lints-guards

Conversation

@jessealama

Copy link
Copy Markdown
Contributor

In anticipation of more work on the weekly Zulip report, I've taken a look at some places where report generation can crash and tried to harden the workflow against failure.

We set continue-on-error in .github/workflows/weekly-lints.yml, which would allow a crash in Zulip report generation to silently succeed. Append to GITHUB_OUTPUT instead of truncating it, fail the job when the build step's outcome isn't success, and on any failure post a notice to the same Zulip topic linking to the run.

@jessealama

Copy link
Copy Markdown
Contributor Author

This is another idea that, like other reporting PRs I've made here, might apply in the new downstream setting. For now, no need to review. I'll convert the PR into a draft.

@jessealama
jessealama marked this pull request as draft September 29, 2026 14:51
@jessealama
jessealama force-pushed the ci/weekly-lints-guards branch from 40ec1f1 to 906a6aa Compare October 5, 2026 03:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant