-
Notifications
You must be signed in to change notification settings - Fork 592
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
Publish steps for docs website #2476
Conversation
Codecov ReportBase: 50.15% // Head: 62.53% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #2476 +/- ##
============================================
+ Coverage 50.15% 62.53% +12.38%
============================================
Files 228 249 +21
Lines 31445 42025 +10580
Branches 343 343
============================================
+ Hits 15770 26282 +10512
- Misses 15675 15743 +68
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@benjaminpkane is there risk that a docs build would fail in the action that would cause an incomplete/corrupted version of the docs to be synced to docs.voxel51.com? Or am I over-analyzing?
I recommend creating new GCS creds specifically for this workflow, just to be proper.
I would consider it unlikely, but if we do want to roll back a re-upload should take less than a minute |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Adds the publishing steps via
gsutil
to automate the release of docs updates. @brimoor is there a cloud storage service account secret we can use? Or I can create one. cc @findtopher