RE: About RawGit, and possible replacements

Ditto, same question and problem.
How to render "working" branches?
Michael McCool (Web of Things WG)

-----Original Message-----
From: Matt King [mailto:a11ythinker@gmail.com] 
Sent: Wednesday, December 12, 2018 09:17
To: 'Tab Atkins Jr.' <jackalmage@gmail.com>; 'Antonio Olmo Titos' <antonio@w3.org>
Cc: w3t@w3.org; chairs@w3.org; spec-prod@w3.org; w3t-sys@w3.org
Subject: RE: About RawGit, and possible replacements

>There's no reason to use any of these; they predate the introduction 
>and subsequent ease-of-use improvements of the GitHub Pages service 
>(aka what you get served when you visit https://username.github.io/reponame/).

If we use gh-pages branch to publish master as our editor's draft, how can we use gh-pages to view work in progress that is not yet merged to master? We primarily use raw.githack to render the version of a document that is in a feature branch.

Matt King

-----Original Message-----
From: Tab Atkins Jr. <jackalmage@gmail.com>
Sent: Tuesday, December 11, 2018 3:36 PM
To: Antonio Olmo Titos <antonio@w3.org>
Cc: w3t@w3.org; chairs@w3.org; spec-prod@w3.org Prod <spec-prod@w3.org>; w3t-sys@w3.org
Subject: Re: About RawGit, and possible replacements

On Tue, Dec 11, 2018 at 7:48 AM Antonio Olmo Titos <antonio@w3.org> wrote:
> as you may know, the free online service RawGit is discontinued, and 
> will stop working for all URLs next year [1].
> This was used by some groups to serve the drafts, documents and other 
> assets that they were hosting on different repositories and branches 
> on GitHub.
>
> A few replacements have emerged lately, like HTML Preview [2], 
> raw.githack.com [3] and Staticaly [4].
> They offer different features and levels of service.
>
> Among these, the Systems Team for now recommend Staticaly -- with the 
> warning that it's just a suggestion that comes with no support or 
> guarantee from us, as it is a third-party service that we do not 
> control.
>
> We have reflected this on our documentation about GH usage and best 
> practices [5].
>
> Talk to us (or, even better, submit an issue or a pull
> request) if you have questions, comments or ideas to contribute.

There's no reason to use any of these; they predate the introduction and subsequent ease-of-use improvements of the GitHub Pages service (aka what you get served when you visit https://username.github.io/reponame/).

Just set up your GH-Pages as desired (you can either serve the gh-pages branch, or the master branch, or the /docs folder of the master branch) and use that to serve things. Using rawgit and related services has been an antipattern for years. Please don't recommend any of these, and change your recommendations to just set up GitHub Pages.

~TJ

Received on Wednesday, 12 December 2018 01:48:53 UTC