Re: Build automation

Thanks, Norm,

When you say the ixml home page, you’re not talking about [1] right?
I noticed that page still referring to the next meeting in April, with an additional reference to a May meeting.
What’s the protocol for updating that page? Happy to help out…

-m

[1] https://www.w3.org/community/ixml/ <https://www.w3.org/community/ixml/> 

> On Jul 5, 2022, at 6:15 AM, Norm Tovey-Walsh <norm@saxonica.com> wrote:
> 
> Hello folks,
> 
> I believe I have successfully setup build automation for the Invisible
> XML home page. On commits to the master branch, we:
> 
> 1. Update the current editorial draft of Invisible XML
> 2. Update the browseable test catalog
> 
> It worked today, but keep your eyes open for issues.
> 
> I’d like to work on refining our workflow further.
> 
> I’m thinking that we should all make commits to the ‘ixml’ repository
> exclusively through approved pull requests. (No more naughty making
> commits directly to the repo.)
> 
> I think we could also use tags to establish what we consider the current
> consensus draft, as distinct from whatever is currently in the editorial
> draft. (That means we can be a little more aggressive about trying out
> changes in the editorial drafts.)
> 
> I also want to setup automatic diffs, but that will require learning how
> to store “secrets” in GitHub workflows and isn’t likely to happen before
> next week, at the earliest.
> 
>                                        Be seeing you,
>                                          norm
> 
> --
> Norm Tovey-Walsh
> Saxonica