When the repository matches the org name, which might be slightly more
common for small OSS projects where the owner wishes to move to using an
org to allow it be managed by other contributors over time, the existing
code will assume this means it is for the org level pages.
Consequently updates to a repo such as vagrant-libvirt/vagrant-libvirt
will have it's preview URL using the org style rather than the
repository style.
This change adjust the matching to limit to only allowing repos of the
name <org>.github.io to be presented with the org style gh-pages
preview URL.
rossjrw
commented
1 year ago
When the repository matches the org name, which might be slightly more common for small OSS projects where the owner wishes to move to using an org to allow it be managed by other contributors over time, the existing code will assume this means it is for the org level pages.
Consequently updates to a repo such as vagrant-libvirt/vagrant-libvirt will have it's preview URL using the org style rather than the repository style.
This change adjust the matching to limit to only allowing repos of the name
<org>.github.ioto be presented with the org style gh-pages preview URL.Fixes #39