Skip to content
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

Correctly parse repo information. #32

Merged
merged 1 commit into from
Mar 17, 2020
Merged

Conversation

rwjblue
Copy link
Owner

@rwjblue rwjblue commented Mar 13, 2020

This leverages the hosted-git-info package, which is used by the npm CLI for parsing these exact strings. This is much better than manually writing a RegExp.

Fixes #31

This leverages the
[hosted-git-info](https://github.com/npm/hosted-git-info) package, which
is used by the `npm` CLI for parsing these exact strings. This is
**much** better than manually writing a RegExp.
Copy link
Collaborator

@hjdivad hjdivad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤘 :shipit:

@rwjblue rwjblue merged commit acef67b into master Mar 17, 2020
@rwjblue rwjblue added the bug Something isn't working label Mar 17, 2020
@delete-merged-branch delete-merged-branch bot deleted the parse-repo-info-correctly branch March 17, 2020 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When repo name ends with .js.git we do not make the issue endpoint call correct
2 participants