Added examples and aligned language within docs/checks/actions.md #1664
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
timburgan
changed the title
timburgan
changed the title
TingluoHuang
approved these changes
Feb 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added some practical examples to the
docs/checkscontent.This pages are linked to in the runner logs when the runner has connectivity issues.
I've added examples to the Actions to connectivity test, guiding users how to test this with
curl, and aligned some formatting with the public GitHub documentation at https://docs.github.com. These updates align with the first troubleshooting steps that users will be requested to perform by GitHub Support.In addition, for GitHub Enterprise Server, I included the common cause of these errors, that the default self-signed TLS certificate is being used rather than a trusted certificate. This will assist administrators with resolving this issue by uploading a trusted certificate to their appliance, or by enabling Let's Encrypt.
Using
[hostname]within the GHES URL also aligns with best-practice from GitHub Support team.