I'm a self-taught dev focused on websites and Python development.
My friends call me the "Data Genie".
When I get bored, I find tech to read about, write about and build things with.
I haven't heard of Jigsaw before and haven't seen the subtree command.
The approach is use for my repos for the commit step is using a popular generic GH Pages action that will work with any given output directory. I covered it in my post here.
Cool, I skimmed your article, looks like a straightforward setup! I mostly went the way I did because I didn't know anything about GitHub Actions when starting out and Jigsaw didn't have much guidance other than the articles I mentioned. All I know is it now works the way it should when I push to master.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for sharing.
I haven't heard of Jigsaw before and haven't seen the subtree command.
The approach is use for my repos for the commit step is using a popular generic GH Pages action that will work with any given output directory. I covered it in my post here.
dev.to/michaelcurrin/github-pages-...
I've also seen other workflows which do the commit step themselves like you do.
Also it would be nice for your to explain -f does a force push to overwrite existing changes.
What is the reason for
origin gh-pages:gh-pagesasorigin gh-pagesis common and should be sufficient.Cool, I skimmed your article, looks like a straightforward setup! I mostly went the way I did because I didn't know anything about GitHub Actions when starting out and Jigsaw didn't have much guidance other than the articles I mentioned. All I know is it now works the way it should when I push to
master.