-
Notifications
You must be signed in to change notification settings - Fork 30
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
Publishing from master instead of main #347
Comments
I think it's something different from that.
|
OK. I thought that had already been merged. Merging #341 will close this issue then. |
#341 is now merged, but someone needs to rebuild/publish the website to see final updates |
I tried to build it, it all runs fine, but I'm not sure it actually includes all of the updates made in #335. |
It might be because of errors in the build? I noticed that |
Maybe, because the changes from #340 are present. |
Is this issue still relevant after #349 was merged? |
Let me try building the website from the source branch and see what happens. |
Based on the terminal output, all the build commands are pointing to the |
With the changes in #345 and #346 it looks like the website is still published from the master branch and not the main branch like it should be. This may be why some of the most recent changes are not captured in the current version of the site.
The text was updated successfully, but these errors were encountered: