Skip to content
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

GitHub Action should not request logs in the same Issue multiple times. #12429

Open
DuckDuckStudio opened this issue Jan 4, 2025 · 4 comments
Assignees

Comments

@DuckDuckStudio
Copy link

Is your feature request related to a problem? Please describe.
In #12428 , I found that whenever I changed the title of an issue, GitHub Action would request the log from me again and add the needs-author-feedback label again, regardless of whether or not I had previously given feedback on the log request.

Describe the solution you'd like
Do not request logs from me again when I have previously given feedback on a log request.

Describe alternatives you've considered
I see that GitHub Action gives the issue author two options (/feature and /question) , and when the issue author gives the appropriate instructions, GitHub Action automatically adds the relevant label to the issue.
Is it feasible to stop requesting logs if the issue has already had the relevant label added?

Additional context
Check out the timeline for #12428 to get an idea of what was going on.

@DuckDuckStudio DuckDuckStudio changed the title GitHub Action should not request logs from the same Issue multiple times. GitHub Action should not request logs in the same Issue multiple times. Jan 4, 2025
Copy link

github-actions bot commented Jan 4, 2025

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

Diagnostic information
Found '/question', adding tag 'question'
Found '/feature', adding tag 'feature'

@DuckDuckStudio
Copy link
Author

/feature

Copy link

github-actions bot commented Jan 4, 2025

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

Diagnostic information
Found '/question', adding tag 'question'
Found '/feature', adding tag 'feature'

Copy link

github-actions bot commented Jan 4, 2025

Diagnostic information
Found '/feature', adding tag 'feature'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants