-
Notifications
You must be signed in to change notification settings - Fork 885
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Best way to push ongoing changes #178
Comments
I have the same question - should I commit to main/master, checkout gh-branch, then deploy? Commit to main and then pull request? |
Hi @nssensalo and @dj-lee1, thanks for asking this question. The way I do it is to store my source code on the |
At least, that is how I used to do it. Nowadays (on my real, work projects), I use GitHub Actions with something like this to build and deploy the app for me whenever I create a new Release on GitHub. |
#push #commits
Which of these applies to you? (Select all that apply)
Step
Which step of the tutorial do you want someone to help you with? (Select one)
Links
Tell us where we can find your code and your GitHub Pages site:
Everything else
You can put whatever you want into this section.
My site is up and running. Moving forwards, what is the best way to publish ongoing changes? Do I " npm run deploy" for every update? If so, I see on the github page commits and pull request for the gh-page branch. Do I NEED to address those ? Beacuse there isn't another comperable gh-pages branch to compare and reconcile with. I just leave it?
Thanks
The text was updated successfully, but these errors were encountered: