Repository navigation
fix(ci): report website rebuild dispatch failures - #103
Merged
Merged
Conversation
ai
reviewed
Oct 15, 2026
| permissions: {} | ||
| jobs: | ||
| deploy: | ||
| if: github.event.deleted == false |
Contributor
Author
There was a problem hiding this comment.
(perf optimization to skip rebuild on tag/branch removing, but we don't need it with branches: -main)
arestov
force-pushed
the
fix/site-rebuild-trigger
branch
from
October 15, 2026 15:26
5bc11ff to
cbf3005
Compare
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
2 participants
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.
Make website rebuild requests fail on HTTP errors or missing credentials instead of silently succeeding. Pass credentials through environment variables, use standard GitHub API headers, and bound request time.
Requires the website receiver in logux/logux.org#64; merge that PR first. This keeps the existing push-to-main trigger and dispatch credentials.
Validation: actionlint and six local Bash/curl scenarios (HTTP 204/401/403/500 and missing username/token).