Failure to use remote info in repo cloned from GitHub Enterprise.

[hartzell]

Running Jekyll on a GitHub Pages compatible site (e.g. documentation-theme-jekyll) fails with this error message ** even when there is an origin remote defined **.

             Error: No repo name found. Specify using PAGES_REPO_NWO environment variables, 'repository' in your configuration, or set up an 'origin' git remote pointing to your github.com repository.

$ git remote -v
origin	git@<elided>.com:<elided>/computing-portal.git (fetch)
origin	git@<elided>.com:<elided>/computing-portal.git (push)

This happens because around line 103 of metadata_drop.rb this snippet of code tries to match the "url" (it's not a URL, but that's another issue...) against a pattern that's hardwired for the public github.

matches = git_remote_url.chomp(".git").match %r!github.com(:|/)([\w-]+)/([\w\.-]+)!

One fix would be to use a library like git-remote-parser and combine it's owner and repo attributes.

If there's an objection pulling in the entire gem, one could either borrow bits (in a way that honor'ed its MIT license) or reimplement them.

Can someone comment on the following?

• Is there any effort to make this gem more useful GitHub Enterprise customers (in which case this issue could tag along on that effort)?

• Would a PR with a fix that used git-remote-parser be acceptable?

• Failing the above, what constraints are there on coding up a fix?

Thanks!

[hartzell]

It seems that much of the info needed to make #48 could be driven by values parsed out of the origin using git-remote-parser, assuming that library is acceptable.

[jabenninghoff]

I'm seeing a similar error, even though I'm using a public GitHub Pages site, with JEKYLL_ENV=production:

             ERROR: YOUR SITE COULD NOT BE BUILT:
                    ------------------------------------
                    No repo name found. Specify using PAGES_REPO_NWO environment variables, 'repository' in your configuration, or set up an 'origin' git remote pointing to your github.com repository.

$ git remote -v
origin	https://github.com/information-safety/information-safety.github.io.git (fetch)
origin	https://github.com/information-safety/information-safety.github.io.git (push)

[jekyllbot]

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.