Update to two folder names to address issue cloning repo#987
Merged
SapphicFire merged 1 commit intoServiceNowDevProgram:mainfrom Oct 29, 2023
Merged
Update to two folder names to address issue cloning repo#987SapphicFire merged 1 commit intoServiceNowDevProgram:mainfrom
SapphicFire merged 1 commit intoServiceNowDevProgram:mainfrom
Conversation
Contributor
Author
|
Accepting own submission as verified on two OSes |
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
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.
Why
When cloning a repository to a local machine, directory structures are bound to supported values in the host OS. However, GitHub allows unexpected values (trailing/leading whitespace, some invalid characters depending on OS.
This fixes #850
What
Updated
Background Scripts/Extend Code Search Base./toBackground Scripts/Extend Code Search Base/Updated
Flow Actions/Get choice field value (mitigating known error) /toFlow Actions/Get choice field value (mitigating known error)/