aboutcode-org / aboutcode-org/purldb

How is vcs_url changed if at all when git_url has a non-https prefix or .git suffix?

Open
#470 0 comments 0 reactions 0 assignees View on GitHub
data
Dominant language
HTML
Stars
67
Forks
69
Avg merge
8d 8h
Merged PRs (30d)
1

Description

Looking at some non-cocoapods `vcs_url` values (generated from `info()` in `fetchcode/package.py`) -- which often come from the `git_url` value in `https://api.github.com/repos/{repo_owner}/{repo_name}` for those PURLs with a GH repo -- I see some that look like this

- for `pkg:github/avahi/avahi@0.8` -- `"vcs_url": "git://github.com/avahi/avahi.git"` (in https://api.github.com/repos/avahi/avahi, we see `"git_url": "git://github.com/avahi/avahi.git"`)

or

- for `pkg:npm/canonical-path@1.0.0` -- `"vcs_url": "git+https://github.com/petebacondarwin/node-canonical-path.git"` (in https://api.github.com/repos/petebacondarwin/node-canonical-path it's slightly different from the `vcs_url` -- `"git_url": "git://github.com/petebacondarwin/node-canonical-path.git"`)

and others like this

- for `pkg:npm/canonical-path@0.0.2` -- `"vcs_url": "https://github.com/petebacondarwin/node-canonical-path"` (as noted just above for @1.0.0, the `git_url` starts with `git:` and ends with `.git`.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.