support: How can I wait for the deploy to be completed before continuing my workflow?

[predominant]

Checklist

• I am using the latest version of this action.
• I have read the latest README and followed the instructions.
• I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your question

Apologies if this is the wrong place to ask. I have a workflow that includes this action in the middle of a workflow. The action immediately after gh-pages, is to trigger a remote server that pulls information from the deployed pages. However, it seems like the gh-pages action finishes and triggers the next step before the gh-pages branch is fully deployed. Adding a manual hardcoded delay of 30 seconds sometimes works, but othertimes is does not. The branch I am deploying contains tens of thousands of files.

How can I wait until the deployment has actually completed?

Relevant links

Public repository: N/A Private company respository
YAML config:
YAML workflow:


      - name: Deploy to GitHub Pages
        uses: peaceiris/actions-gh-pages@v4
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          publish_dir: ./dist
          publish_branch: gh-pages
          destination_dir: ${{ github.ref == 'refs/heads/master' && 'master' || github.head_ref }}
          user_name: 'github-actions[bot]'
          user_email: 'github-actions[bot]@users.noreply.github.com'

Relevant log output

No response

Additional context.

No response

[janbrasna]

This action only pushes the commit to the gh-pages branch — the actual deployment is done by GitHub as a followup workflow (you can check that in your Actions tab, that there's a distinct pages-build-and-deployment separate implicit CI, launching seconds after each commit, and running based on configs for some additional seconds…)

You'd have to base any events off of that runs, but usually chaining CI statuses often means writing some custom hooks based on GH API.

Your best option would be abandoning committing to gh-pages, and switching to native deployment environments that you can actually use immediately for signalling deployment statuses.

[predominant]

Thanks for your feedback