Roblox / cla-signature-bot

GitHub Action for self-contained handling of CLA signatures
Apache License 2.0
14 stars 13 forks source link

Download Problem #20

Open robert-virkus opened 3 years ago

robert-virkus commented 3 years ago

Describe the bug I try to use the CLA-Signature bot with the described configuration. The bot is started but cannot be downloaded. The error message is

Failed to resolve action download info. Error: Unable to resolve action `Roblox/cla-signature-bot@2.0.1`, unable to find version `2.0.1`

I tried the following definitions for uses in the script:

To Reproduce Steps to reproduce the behavior:

  1. Use the script as defined in https://github.com/Roblox/cla-signature-bot/blob/master/README.md
  2. In an existing issue on your repository, add a new comment
  3. Go to the Actions tab of your repository to see the error

Expected behavior GitHub actions should be able to download the bot.

Log

Current runner version: '2.275.1'
Operating System
Virtual Environment
Prepare workflow directory
Prepare all required actions
Getting action download info
Failed to resolve action download info. Error: Unable to resolve action `Roblox/cla-signature-bot@2.0.1`, unable to find version `2.0.1`
Retrying in 20.256 seconds
Failed to resolve action download info. Error: Unable to resolve action `Roblox/cla-signature-bot@2.0.1`, unable to find version `2.0.1`
Retrying in 11.918 seconds
Error: Failed to resolve action download info.
robert-virkus commented 3 years ago

This works for me: uses: roblox/cla-assistant@master

Not sure why this works. Additionally, I changed the

on:
  issue_comment:
    types: [created]
  pull_request:
    types: [opened,closed,synchronize]

to

on:
  pull_request:
    types: [opened,closed,synchronize]

Without it I got this error message: "GraphQL query to get commit authors failed: 'Could not resolve to a PullRequest with the number of 20.'.

Not sure why I needed to reference the branch directly and remove the issue_comment trigger, possibly the documentation should be changed, so I am leaving this issue open for now.