Skip to content

action incorrectly reports nothing to commit #1708

Closed Answered by JamesIves
lucascolley asked this question in Q&A
Discussion options

You must be logged in to vote

You are likely encountering a race condition here. When I look at your workflows, both the build and deploy trigger from the same event (push), meaning that it may be downloading a stale artifact and thus finding that there's nothing to deploy depending on which one finishes first.

You may want to re-arrange your workflows to combine the build + deploy job, or run them both independently, ie build your docs, and then deploy them in the same job. You could also use a workflow_call, or something to signify that the build job has finished before the other one runs, but that may be overkill for this use case.

Something like this:

name: Docs Deploy

on:
  push:
    branches:
      - main

jobs:…

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by JamesIves
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #1707 on September 30, 2024 18:50.