Revise file name restrictions in renaming guide - #45748
Conversation
Updated tip regarding file name restrictions when renaming files via the web interface.
|
This pull request may have been opened accidentally. I'm going to close it now, but feel free to check out our contribution guidelines, or raise an issue. |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
subatoi
left a comment
There was a problem hiding this comment.
Thanks @ashis-baral—good find and apologies about the same situation with the automatic closure. I'll get this merged now
|
@subatoi Thank you! No worries, and I really appreciate you taking the time to review and merge the correction.👍 |
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
The file name restriction in the Renaming a file article is inaccurate/misleading.
Renaming a File on Github
This PR removes the following incorrect statement:
Check off the following: