docs
docs copied to clipboard
rewrote sentence #22874
Why:
I rewrote a sentence to make it shorter (with a recommended sentence from the issue information.)
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following:
- [x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
- [x] For content changes, I have completed the self-review checklist.
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
Automatically generated comment ℹ️
This comment is automatically generated and will be overwritten every time changes are committed to this branch.
The table contains an overview of files in the content
directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data
directory will not show up in this table.
Content directory changes
You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
Source | Preview | Production | What Changed |
---|---|---|---|
developers/webhooks-and-events/webhooks/securing-your-webhooks.md |
fpt ghec ghes@ 3.7 3.6 3.5 3.4 3.3 ghae |
fpt ghec ghes@ 3.7 3.6 3.5 3.4 3.3 ghae |
fpt: Free, Pro, Team ghec: GitHub Enterprise Cloud ghes: GitHub Enterprise Server ghae: GitHub AE
@brubru6707 Thanks for opening a PR! 👍
You mentioned that this information came from the issue information. Would you mind linking the issue you are referencing? For more information about linking issues, see "Linking a pull request to an issue".
That will really help in getting this PR triaged and reviewed ✨
@brubru6707 Thank you for updating the post and including the issue! ✨
Looking at the issue, it looks like we do have a PR waiting for review with this fix from last week. So this would be considered a duplicate PR. Because of that, I'm going to go ahead and close this PR 💛
If, for whatever reason, the first PR isn't accepted, I'll reopen this one. Please take a look at our help wanted section to find more open issues you can work on.
Thank you for your interest in improving GitHub Docs! :sparkling_heart: