-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIX: issues with ioc-deploy casing #196
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm on board with this on the whole 👍
I also ended up adding a check for readmes like this one that have the last part of the suffix in them but not the ioc-area part: https://github.com/pcdshub/ioc-common-ads-ioc/blob/master/README.md |
Testing for this has been lots of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 👍
Thank you for the reviews! |
Description
Fix an issue where
ioc-deploy
would happily create new folders if you make a casing typo, e.g.ioc-common-gigecam
will now deploy toioc/common/gigECam
.Github URLs are case-insensitive, e.g. you can clone
ioc-coMMon-GiGeCaM
and it will work just fine.So, we need to turn to other sources for the correct casing for directory deployment.
The REST API is the most consistent method, but it requires additional authentication.
This PR checks two things in order looking for a match:
Motivation and Context
https://jira.slac.stanford.edu/browse/ECS-6018
How Has This Been Tested?
Interactively only, works as I expect
Where Has This Been Documented?
Here only