Skip to content

ci: notify the docs portal after deploy #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kartikeya-27 merged 1 commit into from
Sep 6, 2026
Merged

ci: notify the docs portal after deploy #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .github/workflows/docs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,3 +71,16 @@ jobs:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v5

# Rebuilds docs.byteveda.org/dagron/ now instead of at the portal's next
# cron. The run id is passed because this run is still in progress here, so
# the portal cannot find it as the latest successful docs.yml run — it would
# mirror the build before this one.
- name: Notify docs portal
env:
GH_TOKEN: ${{ secrets.DOCS_DISPATCH_TOKEN }}
run: |
gh api repos/ByteVeda/byteveda.site/dispatches \
-f event_type=tool-docs-published \
-f "client_payload[slug]=dagron" \
-f "client_payload[run_id]=${{ github.run_id }}"