-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting started not working #49
Comments
Using this exact yaml: name: "command demo"
# the workflow to execute on is comments that are newly created
on:
issue_comment:
types: [ created ]
# permissions needed for reacting to IssueOps commands on issues and PRs
permissions:
pull-requests: write
issues: write
checks: read
jobs:
demo:
runs-on: ubuntu-latest
steps:
# execute IssueOps command logic, hooray!
# this will be used to "gate" all future steps below
- uses: github/command@main
id: ping
with:
command: ".ping"
# run your custom logic for your project here - example seen below
# conditionally run some logic here
- name: ping command
if: ${{ steps.ping.outputs.continue == 'true' }}
run: echo 'Got comment in PR \#${{ steps.ping.outputs.issue_number }} with params ${{ steps.ping.outputs.params }}' Commenting on this pull request: GrantBirki/actions-sandbox#127 (comment) I get results that are expected: https://github.com/GrantBirki/actions-sandbox/actions/runs/12291435545/job/34300203115 I'm not sure why you are getting that error but it is almost always related to your workflow not having the correct |
I moved to branch deploy so didn't tried (nor debugged this) however I'll run it again to confirm or close the issue. In any case the AI pull request is not so bad 😉 |
I made it work by adding the |
Describe the Issue
I'm trying this action in an empty repository and I'm not able to make it working. It says something about missing permissions but it's not specifying which one is missing.
I put the attached workflow in main branch, then I opened a pull request and commented it with
Action Configuration
Relevant Actions Log Output
Extra Information
It would be very useful if the action uses some
core.debug
calls in its codebase to better track issues like this one. At the moment even with debug mode there is no output from the action itself.The text was updated successfully, but these errors were encountered: