fix: fix hubConfigured for GitHub Actions

[eunjae-lee]

closes #316

[eunjae-lee]

@uetchy Hi there,
Since I don't have access to GitHub actions, I cannot test this by myself :(
For now, the easiest way to fix this issue seems to be using hub release instead of hub api user.
What do you think?
Will this work? Could you test this for me if you don't mind?

[uetchy]

hub release would work for verifying token but not verify it is privileged to create a release on a repository.
Checking the result of hub api repos/<user>/<repo> | jq .permissions.push might work; If it returns true, it means with provided GITHUB_TOKEN you can create a release on the repo. Perhaps it is easier to use octokit module than hub to do such a task.
Anyway I'll test this PR on my own project to see what happens.

[uetchy]

Is it possible to publish this PR as an npm module?

https://www.pika.dev/cicd

EDIT:
Already possible with npm i algolia/shipjs#fix/gh-action

[uetchy]

btw npm i algolia/shipjs#fix/gh-action end up failing with error: /bin/sh: 1: rollup: not found
https://github.com/vibranthq/opinionated-review/commit/50982441dfa47e49206680e5a0821dafb71cee97/checks?check_suite_id=297781477#step:6:10

EDIT:
Because prepare script is a reserved command for npm then it will be invoked when run npm install with git URL. AWESOME.
https://docs.npmjs.com/misc/scripts

EDIT:
End up cloning repo and manually build package but it finally succeeds.

- run: |
          git clone https://github.com/algolia/shipjs
          cd shipjs
          git checkout fix/gh-action
          cd packages/shipjs
          yarn install
          yarn global add file:$PWD
          echo "::add-path::$HOME/.yarn/bin"
      - run: |
          shipjs prepare

[uetchy]

Finally, it worked out
https://github.com/vibranthq/opinionated-review/commit/65868256d0b6dd7f0c876535c9406610850583ca/checks?check_suite_id=297897496

[uetchy]

🚀

[eunjae-lee]

hub release would work for verifying token but not verify it is privileged to create a release on a repository.
Checking the result of hub api repos/<user>/<repo> | jq .permissions.push might work; If it returns true, it means with provided GITHUB_TOKEN you can create a release on the repo. Perhaps it is easier to use octokit module than hub to do such a task.

Thanks for the test 🚀
And thanks again for the explanation.
At the moment, verifying token sounds enough and we can add code later to check if the token is privileged to create release when needed.