-
-
Notifications
You must be signed in to change notification settings - Fork 843
Updates CONTRIBUTING.md Docker WSL troubleshooting. #8172
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
Updates CONTRIBUTING.md Docker WSL troubleshooting. #8172
Conversation
Adds tip to check that the version of Go to see if it may be a buggy older version.
|
Want to review this pull request? Take a look at this documentation for a step by step guide! Note that CONTRIBUTING.md cannot previewed locally; rather it should be previewed at this URL: |
|
Availability: Monday - Friday, 10:00 AM to 4:00 PM JST |
rogerioduenas
left a comment
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.
Hi @ryanfkeller !
Great job with this pull request!
- The branching was done correctly.
- Issue number was listed.
- The PR title is descriptive of the changes.
- Changes were made correctly in the code and in the link to the
CONTRIBUTING.mdprovided in the contributor's branch. - Relevant images were included to show visual changes.
- The PR request clearly states what was updated.
Again, great work and thanks for taking the time to contribute to the website!
|
ETA: 6/6 EOD |
andyvu923
left a comment
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.
Hey @ryanfkeller , thanks for working on this issue!
Things done well
- Correct branches were used
- PR links issue
- Visuals are provided
- Code changes clean and relevant to issue
LGTM, PR approved! 👍👍
Fixes #7642
What changes did you make?
Why did you make the changes (we will use this info to test)?
CodeQL Alerts
After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.
Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown
Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.
Instructions for resolving CodeQL alerts
If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.
In general, CodeQL alerts should be resolved prior to PR reviews and merging
Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)
Visuals before changes are applied
Visuals after changes are applied