remove leading whitespace from filenames #105
Merged
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
|
@vintagesucks Thank you so much for taking care of it! Could I ask you to update their content with the proper information too? |
|
@mehrancodes I have taken care of the duplicate licence file, but I don't think the creation of contribution guidelines is something I can do for you. |
jotaesteves
approved these changes
May 21, 2024
mehrancodes
approved these changes
May 21, 2024
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.
Both CONTRIBUTING.md and LICENSE.md, which are linked from the README, currently return 404 because the filenames contain leading whitespace.
Example
CONTRIBUTING.md:Note: Both files are also empty, but I didn't want to include a README change to fix the LICENSE link in this PR as well.