simplify instructions to use provided github token

[jaredh159]

thanks for the action!

the automatic ${{ github.token }} var that every action is provided is sufficient to be the access_token so you can remove a couple of the steps, making integrating this even easier.

[styfle]

I don't think this is the case considering #11

[jaredh159]

that issue seems to be someone who got a wrongly scoped token. from what i read i think github gives you a token that has permission for the repo that is running the action, which should mean it should work fine for a private repo. maybe i'll do a quick test of that theory though...

…

On Thu, Apr 30, 2020 at 4:02 PM Steven ***@***.***> wrote: I don't think this is the case considering #11 <#11> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVZNOU34AYELDFRTA63TTLRPHKLRANCNFSM4MWQICFA> .

[pauldps]

Using github.token worked for me. I have a private repo with a Ruby build workflow. I added the extra job from this using github.token and the outdated jobs were cancelled as expected.

[styfle]

Confirmed, this works in #13 👍