chore: gh-pages does not exist message for doc-deploy-dev

[klmcadams]

Create branch if it doesn't exist in doc-deploy-dev and doc-deploy-stable

Create new gh-pages branch: CI · ansys-internal/pytemplate-sandbox@cc726c4 (github.com)
Update existing gh-pages branch: CI · ansys-internal/pytemplate-sandbox@cc726c4 (github.com)

Create new unique branch: specify branch · ansys-internal/pytemplate-sandbox@eb14ba3 (github.com)
Update existing unique branch: CI · ansys-internal/pytemplate-sandbox@eb14ba3 (github.com)

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[RobPasMue]

Can we not just fix this in the doc-deploy-* actions? I'd prefer fixing it rather than just informing

[SMoraisAnsys]

Can we not just fix this in the doc-deploy-* actions? I'd prefer fixing it rather than just informing

Agreeing with @RobPasMue, it would be great for new maintainers trying to use ansys actions.

[jorgepiloto]

It would be great if we could check if the input branch exists in the origin. If not, the script creates and pushes it before uploading the content.

[SMoraisAnsys]

Just wondering if handling non existing branch creation couldn't be performer more simply. Would it be possible to follow the following workflow :

1. create the branch locally (git checkout --orphan ${{ env.BRANCH }})
2. configure git (since it seems to be required)
3. push without commit (git push origin ${{ env.BRANCH }}:${{ env.BRANCH }})

If the branch exists, could a simple git switch ${{ env.BRANCH }} do the trick ?

[klmcadams]

Hi @SMoraisAnsys, I tried following those steps only but ran into a few issues:

• When trying to push without commit I got this error: "error: src refspec gh-pages does not match any. "
  • When I looked up how to solve this issue, it said to add a commit and then push
• It wasn't able to switch to the existing gh-pages branch bc I got this error: "fatal: invalid reference: gh-pages"
  • I looked it up and it said to do a fetch, so I added that command before switch
• Without git rm --cached -r . and git clean -fd, extra files are added to the gh-pages branch even though we are doing an orphan checkout (see pic below)

[SMoraisAnsys]

Hi @SMoraisAnsys, I tried following those steps only but ran into a few issues:

• When trying to push without commit I got this error: "error: src refspec gh-pages does not match any. "

  • When I looked up how to solve this issue, it said to add a commit and then push

• It wasn't able to switch to the existing gh-pages branch bc I got this error: "fatal: invalid reference: gh-pages"

  • I looked it up and it said to do a fetch, so I added that command before switch

• Without git rm --cached -r . and git clean -fd, extra files are added to the gh-pages branch even though we are doing an orphan checkout (see pic below)

Thanks for trying the suggestion and letting me know of the associated limitations !

[SMoraisAnsys]

Hi @SMoraisAnsys, I tried following those steps only but ran into a few issues:

• When trying to push without commit I got this error: "error: src refspec gh-pages does not match any. "

  • When I looked up how to solve this issue, it said to add a commit and then push

• It wasn't able to switch to the existing gh-pages branch bc I got this error: "fatal: invalid reference: gh-pages"

  • I looked it up and it said to do a fetch, so I added that command before switch

• Without git rm --cached -r . and git clean -fd, extra files are added to the gh-pages branch even though we are doing an orphan checkout (see pic below)

Thanks for trying the suggestion and letting me know of the associated limitations !

Just a though but it makes sense that it doesn't work without commiting. AFAIK, branch are references to commits. Thus it would be strange to being able to publish an orphan branch without commiting first. Should have though about that before...

[RobPasMue]

Let's try and get this merged

[RobPasMue]

@jorgepiloto - please approve whenever you get the chance. I believe your suggestions were addressed

[SMoraisAnsys]

Thanks again for this improvement !

[jorgepiloto]

Thanks for the hard work, @klmcadams. Merging and patch-releasing this.