Cases when `make customize` gets incorrect repo URL?

[janbrasna]

I'm wondering how make customize actually happened to pull something that would look like a bare repo (*.git) path for the origins, as here: mozilla/mozilla-headline-type@d4c514c it looks like it inferred exactly that.

(Using this value for all the paths e.g. on the deployment apparently renders broken links then, unfortunately…)

Any ideas what could have been done incorrectly? — or if there could be an enhancement to make that heuristic step here a bit more resilient?

[janbrasna]

Basically, how fragile it would be, if that ".git" was excluded right in the regexp?

googlefonts-project-template/scripts/customize.py

Line 46 in f70fd34

m = re.match(r"(?:https://github.com/|git@github.com:)(.*)/(.*)/?", str(my_repo_url))

Thinking lazy matching to not capture too greedy, something along the lines:

r"(?:https://github.com/|git@github.com:)([^/]+)/([^/]+?)(?:\.git)?/?"

---

BTW, you can't literally name your repos with that .git included (for .git.git bare), so it should be safe from that perspective of false positives.