> **Opportunity for improvement:** > > 1. First of all I find it a bit confusing to have builds on both Travis and > GitHub Actions. If we ever get the time it might be a good idea to refactor > this. This is especially important because the build process must be > maintained ATM in 2 places, meaning I had to make changes to 2 files to fix > this issue this time round.
Last spring I made PR cf-convention/cf-conventions#251 to add the GitHub Action to make sure the doc build was checked on each PR. One reason I went with GitHub Actions over extending the existing Travis build is that it makes it relatively easy to generate previews for PRs in the form of downloadable artifacts. It would be relatively straight forward (famous last words 😃) to fully migrate the Travis build to GitHub Actions, and I would be happy to do that work. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/295#issuecomment-687237543 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
