Fix Windows-incompatible ISO27001 paths#341
Open
Mondotrasho wants to merge 1 commit into
Open
Conversation
Author
|
Let me know if you would prefer if I re did these edits in a branch and opened a new PR rather than from a fork. Fairly new to PR process. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Renames the ISO27001 folder and main Markdown file to remove colons from their paths.
Attempts to clone the repository on Windows using both the Git CLI and GitHub Desktop failed because these paths are not Windows compatible.
Changes
Context
The folder was introduced in #334 and the main file was renamed in #338.
Testing
npm run buildsuccessfully.