Fix index workflow: schedule belongs under on, not concurrency - #201
Merged
Conversation
The concurrency block added in #195 was inserted before the existing schedule trigger, which left schedule nested under concurrency. The file stayed valid YAML, so the pre-merge check passed, but GitHub rejects it as an invalid workflow, and every index run since has failed before creating a job. The live site has therefore been stale since then. Validated with actionlint. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
Preview for this PR has been removed (PR closed). |
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
1 participant
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 index workflow has failed on every push since #195 merged, so notebooks.dandiarchive.org is stale (it still shows the pre-rename title). Cause: the
concurrencyblock added in #195 was inserted ahead of the existingscheduletrigger, leavingschedulenested underconcurrency. That is valid YAML, which is why the pre-merge check passed, but an invalid workflow for GitHub, which fails the run before any job is created. This movesscheduleback underon. Validated with actionlint (its only remaining note is the pre-existingpeaceiris/actions-gh-pages@v3deprecation warning, which is a separate, non-urgent update).Merging triggers a push-event render, which brings the site current with master (rename, newest-first ordering, mobile layout, 001528).
🤖 Generated with Claude Code