Add github workflow to update files from GEDCOM repo

FamilySearch / GEDCOM.io

Files for the GEDCOM.io website

2 stars 5 forks source link

Add github workflow to update files from GEDCOM repo #119

Closed dthaler closed 8 months ago

dthaler commented 9 months ago

Currently this workflow updates the master branch when the GEDCOM repository's main branch is updated. If we instead only want to do it when we do a "release", it's easy to update the workflow to do that instead, by using (say) a tag in the GEDCOM repository.

However, I think it would be useful to generate a live update even if it's in a separate branch of GEDCOM.io so one can see the latest unreleased copy.

dthaler commented 9 months ago

Discussion: only on release Quick rendering on non-release (not for the website) is useful, should it be in GEDCOM or GEDCOM.io?

dthaler commented 8 months ago

I'm thinking we should have 3 branches updated in GEDCOM.io:

Doing a GEDCOM release updates GEDCOM.io "main" branch
Any checkin to GEDCOM main updates GEDCOM.io "next-patch" branch
Any checkin to GEDCOM next-minor updates GEDCOM.io "next-minor" branch

dthaler commented 8 months ago

This workflow now does (weekly):

Update the main branch from the latest FamilySearch/GEDCOM release version, if not already up to date
Update the next-patch branch from the FamilySearch/GEDCOM main branch, if not already up to date
Update the next-minor branch from the FamilySearch/GEDCOM next-minor branch, if not already up to date