-
Notifications
You must be signed in to change notification settings - Fork 1
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
Test #2
Test #2
Conversation
🧪 Heal Test ResultsSummary
##View Details: https://app-staging.heal.dev/projects/Wen/suites/455/executions?executionId=3353 |
README.md
Outdated
| `payload` | ❌ | Optional. If empty, all stories under the suite will be run.| | ||
| `wait-for-results` | ❌ | Whether to wait for results (default: `yes`). | | ||
| `domain` | ❌ | (default: `https://api.heal.dev`). | | ||
| `github-token` | ❌ | GitHub token for PR comments (optional). | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to do the same with the pull-requests
permission ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found that in action.yml, permissions can’t be directly specified for the github-token. Instead, permissions like pull-requests are set at the workflow level where the action is triggered.
🧪 Heal Test ResultsSummary
Failed Tests
|
🧪 Heal Test ResultsSummary
Failed Tests
|
🧪 Heal Test ResultsSummary
Failed Tests
|
#1