55ed60b9fc
Many people open bug reports or feature requests in the `actions/runner` repository that are more generally about GitHub Actions. Often changes in GitHub Actions are cross-cutting across multiple teams or feature areas, so it's best if we direct people to the more general areas (Actions Community Support or GitHub Feedback) so that we can get the most eyes on the problem and give the quickest response.
1.6 KiB
name, about, title, labels, assignees
| name | about | title | labels | assignees |
|---|---|---|---|---|
| 🛑 Report a bug in the runner application | If you have issues with GitHub Actions, please follow the "support for GitHub Actions" link, below. | bug |
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Go to '...'
- Run '....'
- See error
Expected behavior A clear and concise description of what you expected to happen.
Runner Version and Platform
Version of your runner?
OS of the machine running the runner? OSX/Windows/Linux/...
What's not working?
Please include error messages and screenshots.
Job Log Output
If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.
Runner and Worker's Diagnostic Logs
If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.