search

newwwie / newwwie.com

The source for newwwie.com website. The front door to the Newwwie Slack and tech + digital creative community.
https://newwwie.com/
MIT License
15 stars 23 forks source link

Github Pages Deployment #89

Open JayRovacsek opened 1 year ago

JayRovacsek commented 1 year ago

Currently the Github pages deployment stems from the 'master' branch - is the project open to this being moved to an alternate branch is generally common (but not required) pattern? This would have a benefit of not including a large number of commits as result of the build/publish process in the development (master) branch

neozenith commented 7 months ago

Not sure I follow what you mean here? But reducing the volume of commits with our janking hombrewed automated CMS is very welcomed

neozenith commented 7 months ago

This is related to #92

neozenith commented 7 months ago

Looking into this further, the current setup is using branch based deployment.

Which in August 2022 got converted to a default Jekyll based GHAction. 🤮

Also I think part of what @JayRovacsek is describing is that the convention is the published branch is gh-pages and that branch should be purely the deployed output of artifacts.

Whilst main is the source code to generate the website.

It seems it could be streamlined to a more minimal GH Actions workflow.

https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#publishing-with-a-custom-github-actions-workflow

which is effectively these GH Actions / Steps

which should deploy to a github-pages Environment

this doesn’t address the many commits to update the “CMS” though.

neozenith commented 7 months ago

Actually it would address the many commits issue (sort of).

If gh-pages is the deployment branch, then it is purely built artefacts as commits. This is the branch that’ll keep auto updating the nightly events scraping.

main will be purely source code changes.