[HN Gopher] Access Control for GitHub Pages
       ___________________________________________________________________
        
       Access Control for GitHub Pages
        
       Author : jbredeche
       Score  : 63 points
       Date   : 2021-01-22 18:49 UTC (4 hours ago)
        
 (HTM) web link (github.blog)
 (TXT) w3m dump (github.blog)
        
       | abhinav22 wrote:
       | This is great news
        
       | pwdisswordfish5 wrote:
       | > With an internal repository, everyone in your enterprise will
       | be able to view the Page with the same credentials they use to
       | login to github.com
       | 
       | Public service announcement: "login" is a noun; as a verb, you
       | should write "log in". (Consider "knockout" vs. "knock out".)
       | Another thing to watch out for: writing "setup" instead of "set
       | up".
        
         | tshaddox wrote:
         | If you're fond of this rule and want to remember to follow it,
         | just consider how you would write the past tense of the verb.
        
         | hanniabu wrote:
         | Wow, thank you for clarifying this. I was actually wondering
         | about this yesterday and just figured they could be used
         | interchangeably but I also knew that in certain cases writing
         | it a certain way just made more sense but I never knew the
         | noun/verb rule behind it. I feel stupid now lol.
        
       | wjdp wrote:
       | Been using the same feature on GitLab for quite a while for
       | publishing code coverage reports.
        
       | bewuethr wrote:
       | To clarify, this only applies to GitHub Enterprise - great for
       | intranet sites. If you are on GitHub Enterprise.
        
         | petepete wrote:
         | Ah damn, got excited by the headline for a moment there.
         | Thought we'd have another excuse to switch away from
         | Confluence.
        
         | theptip wrote:
         | That's annoying. As far as I can tell this is a free feature in
         | GitLab, and it's one of the ones I miss after moving back to
         | Github.
         | 
         | https://docs.gitlab.com/ee/user/project/pages/pages_access_c...
        
         | beckingz wrote:
         | Look forward to the day when GitHub pages and sharepoint sites
         | can be one and the same.
        
       | sn1de wrote:
       | Baffling that this wasn't a day one feature. Doubly baffling that
       | it now launches on Enterprise only with no guidance on if or when
       | it will be generally available. Never an explanation why this
       | couldn't have been there all along. You have it with the repos
       | already. It almost seems like you would have to go out of your
       | way _not_ to have this baked in from day one. I 'm a long term
       | fan, but c'mon github, you're better than this.
        
         | jrockway wrote:
         | I'm not that baffled, I guess. I would assume Github pages work
         | something like "compile to HTML, push to a CDN" whereas Github
         | itself queries a bunch of data from a database, reads the Git
         | repo itself, etc. -- it's not a static page that can be served
         | from a CDN, the page is generated by an application. Therefore,
         | in the repo case it is easy to check authorization among the
         | other things the page generation code does, whereas for static
         | pages, there is currently no application code that runs for
         | every request, and so no place to put an authorization check.
         | 
         | Obviously you could make the Github Page load a dynamic page
         | that checks auth, but I guess they wanted scalability more than
         | they wanted features, and that's what we arrived with.
         | 
         | TL;DR: I'm not that baffled. If a feature isn't in the spec,
         | you shouldn't expect an implementation that makes it easy to
         | add that feature.
        
       | prepend wrote:
       | This is really great news and I've been waiting for a while.
       | 
       | I use this extensively on gitlab and these little pages sites are
       | easier to use than markdown.
       | 
       | However one thing that's cool about GitLab is that we host it
       | internally so any "public" site is available to anyone on the
       | intranet without needing to log in. So the project sites started
       | getting read by lots of users who don't have GitLab logins and
       | would never commit to a repo.
       | 
       | I wish there was a way to link my orgs logins with GitHub so non-
       | GitHub licensed users could view the sites. I mean, I can do that
       | but I have to then buy GitHub licenses and make them create
       | GitHub accounts just to view project docs. That's pretty
       | expensive compared to just keeping projects on my internal
       | GitLab.
        
       ___________________________________________________________________
       (page generated 2021-01-22 23:00 UTC)