Skip to content
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

Don't deploy old docs site on every merge to main #1626

Merged
merged 1 commit into from
Jun 30, 2023

Conversation

itowlson
Copy link
Contributor

We can still manually deploy it if it ever changes

Copy link
Contributor

@fibonacci1729 fibonacci1729 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we make a note somewhere, something like "MANUALLY DEPLOY DOCS IF MAKING A CHANGE OR ELSE".

@itowlson
Copy link
Contributor Author

@fibonacci1729 @endocrimes learneded me about keeping the auto action but only triggering on relevant changes so I'm gonna do that instead

@itowlson itowlson force-pushed the old-website-skip-auto-deploy branch from ef4b2ad to 046f02c Compare June 29, 2023 22:51
@itowlson itowlson merged commit 90641b2 into fermyon:main Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants