fix: repoURL matching is case sensitive #61
Merged
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.
this change is currently untested, I plan on conducting a full one soon
While testing this awesome project in my own repository, I found that using different casing in the application
repoURL
results in a confusing error message printing that therepoURL
key was missing entirely. We may want to consider printing something more helpful in that case (for example, "Different 'repoURL' under spec.source in file {}")Additionally, I fixed the debug message printing
spec.sources[]
as the source even whenspec.source
is used, which mislead me at the start. (=> rebase)