Add support for absolute paths

[koppor]

      - name: Deploy docs to gh-pages
        uses: peaceiris/actions-gh-pages@v3
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          PUBLISH_BRANCH: gh-pages
          PUBLISH_DIR: /tmp/out

Results in

 ENOENT: no such file or directory, scandir '/home/runner/work/user-documentation/user-documentation/tmp/out'

I assume that the first slash is just stripped?

[peaceiris]

It comes from this line:

actions-gh-pages/src/git-utils.ts

Lines 40 to 43 in c1bc06c

	const publishDir = path.join(
	`${process.env.GITHUB_WORKSPACE}`,
	inps.PublishDir
	);

Currently, this action just supports the directories under the ${GITHUB_WORKSPACE}. We will support the absolute path.

[misfir3]

FYI, I also get this same error when using the relative ./public path, but my hugo files are also one level in, so in my actions workflow, I do the following:

      # change dir and build
      - name: Build
        run: cd hugo-dir && hugo --cleanDestinationDir && cd ../

      - name: Deploy
        uses: peaceiris/actions-gh-pages@v3
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          publish_branch: gh-pages
          publish_dir: ./public

Is this likely the same issue here? Also, I was getting the same error w/o cd ../ (which should actually work)

[peaceiris]

@misfir3 There is a misunderstanding about a step. For each step starts from GITHUB_WORKSPACE so cd ../ is not necessary. The correct setting is the following:

      - name: Build
        run: cd hugo-dir && hugo

      - name: Deploy
        uses: peaceiris/actions-gh-pages@v3
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          publish_dir: ./hugo-dir/public

[misfir3]

thanks @peaceiris - figured out my mistake after posting ☝️ and have it sorted now. Sorry for the noise and thanks for the work on this action!

[peaceiris]

The v3.6.4 has been released and the v3 tag has been updated.

[github-actions]

This issue has been LOCKED because of it being resolved!

The issue has been fixed and is therefore considered resolved.
If you still encounter this or it has changed, open a new issue instead of responding to solved ones.

Log | Bot Usage