Retrofiting an existing repository

[aaronbell]

I'm looking to retrofit existing repositories to the UFR model, and noted that part of the github workflow script creates the fontbakery / proofing documents, then commits them to a separate branch gh-pages.

This requirement seems fine when creating a new repro to house the fonts, or where we are the owner of the repro, but it becomes a hassle when retrofitting a repro owned by someone else because it will require the repro owner to not just merge the PR, but also (a) create a new branch and (b) empty that branch of all content (to keep it clean and follow UFR template model). And if they don't, then every time the repository is updated, they'll receive a "workflow fail" notification. So it is a hassle for the owner either way.

Is there a way that these fontbakery / proofing results / artefacts could be merged in a self-contained way (as in, to the main branch) to make things simple? Or should I just get rid of the automatic workflow process for these sorts of situations? Or are we just expecting owners to create the extra branch?

[vv-monsalve]

Is there a way that these fontbakery / proofing results / artefacts could be merged in a self-contained way (as in, to the main branch) to make things simple?

It could be great, or reported in a new Issue, similarly to what gftools qa allows when using the command gftools qa -f Allison-Regular.ttf --fontbakery --out-url https://github.com/googlefonts/allison