On Fri, 2 May 2025 at 14:57, Niall Pemberton <niall.pember...@gmail.com> wrote:
>
> On Fri, 2 May 2025 at 11:37, sebb <seb...@gmail.com> wrote:
>
> > On Fri, 2 May 2025 at 09:00, Niall Pemberton <niall.pember...@gmail.com>
> > wrote:
> > >
> > > On Thu, 1 May 2025 at 23:29, sebb <seb...@gmail.com> wrote:
> > >
> > > > There is a lot of overlap and duplication in the various Process pages.
> > > >
> > > > They need re-organising.
> > > >
> > >
> > > I agree and its mostly on one page. I was thinking it might be better to
> > > break it up into more pages.
> > >
> > > I was thinking about creating a branch to try out a few ideas - we could
> > > stage it for review & feedback - without messing up the live site. Would
> > > need to adjust the workflow to just generate the site and not do all the
> > > banner processing. Perhaps one "experimental" branch for everyone or
> > > separate one for specific features.
> >
> > That's a good idea, but care needs to be taken to ensure that the
> > correct branches get updated.
> >
> > There are 2 output branches to consider
> > - asf-site
> > - cwiki-retired
> >
> > I think it would be useful to generate both, though cwiki-retired
> > could be added to the site branch rather than a separate branch.
> > This would allow the output to be checked.
> >
>
> I think we're saying the same thing - but we just need to generate to the
> output folder in the branch and serve from there - no need to
> checkout/update any other branch. If the output folder is "commited" into
> the branch, then can check both "flagged" and "cwiki_retired" folders.
>
> It would be good to have a conditional workflow where it runs one thing
> when the branch is "main" and just a simple build when its not. That way,
> we don't have to change the workflow for every feature branch we create.
> Theres an example here:
> https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/using-conditions-to-control-job-execution#example-only-run-job-for-specific-repository
>
Done, I think.
Any feature branch will need a suitable .asf.yaml staging entry with
profile and whoami.
For example:
feature-x branch:
.asf.yaml:
staging:
profile: feature-x
whoami: feature-x
Note that _ is not valid for DNS, so cannot be used in the profile
which is used in the host name.
> Niall
>
>
> > > Niall
> > >
> > >
> > > >
> > > > Sebb
> > > >
> >
