GHC proposals not rendering

[Joachim Breitner]

Hi,

yes, I enabled that PR preview feature yesterday, but it seems that I
also have to grand permissions to their OAuth App to the ghc-proposals
github org … done. 

Hmm, now every PR that isn’t based on a recent master is red, because
it lacks the configuration. Also not nice. Maybe I should disable this
again? At least until the readthedocs setup and output is satisfying
(numbering etc. – any volunteers?)

Cheers,
Joachim

Am Dienstag, dem 23.01.2024 um 10:16 +0000 schrieb Michael Peyton
Jones:
> > If you got the readthedocs site working, that does provide per-PR previews of the built documentation relatively easily.
> > 
> > M
> > 
> > On Tue, Jan 23, 2024 at 8:37 AM Tom Ellis <tom-lists-haskell-cafe-2023 at jaguarpaw.co.uk> wrote:
> > > > On Mon, Jan 22, 2024 at 08:30:47PM -0500, Ben Gamari wrote:
> > > > > > > > On 22/01/2024 16:15, Simon Peyton Jones wrote:
> > > > > > > > > > Is there any workaround at all?   E.g. a web site where you can give it 
> > > > > > > > > > a URL for a RST file,  and it'll typeset the RST for you?  Or is it 
> > > > > > > > > > impossible to to typeset RST?
> > > > > > > > 
> > > > > > > > I tend to use pandoc to preview RST files locally. There are also a few 
> > > > > > > > websites that allow you to enter RST content directly and see a live 
> > > > > > > > preview (e.g. https://snippets.documatt.com/). They may not exactly line 
> > > > > > > > up with how GitHub renders things, of course, and I don't know of any 
> > > > > > > > that let you feed in a URL to an RST file hosted elsewhere.
> > > > > > > > 
> > > > > > As noted during the SWG meeting today, I suspect that the easiest way
> > > > > > forward here may be to just render PRs via CI. However, I don't know how
> > > > > > easy it is to preserve artifacts such that they are viewable using
> > > > > > GitHub Actions. Jose will have a quick look at this.
> > > > 
> > > > Perhaps the artifacts could be deployed as Github Pages.  But in the
> > > > first instance I like Bryan's suggestion of just splitting the
> > > > documents into small-enough pieces.
> > > > _______________________________________________
> > > > ghc-devs mailing list
> > > > ghc-devs at haskell.org
> > > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> > _______________________________________________
> > ghc-devs mailing list
> > ghc-devs at haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

-- 
Joachim Breitner
  mail at joachim-breitner.de
  http://www.joachim-breitner.de/