Fix: Handle .git extensions in repository URLs #41
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.
Fixing an error reported #32 (comment)
The main issue was that one of the plugins in the config file had a .git extension at the end of the repository URL.
awesome-nu/config.yaml
Line 235 in 65af689
To address this issue, we implemented two steps:
.git
extensions with an empty string in URLs, ensuring that the script can correctly locate theCargo.toml
file.