Workflow to publish Backstage TechDocs #156
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Andre Wanlin <[email protected]>
awanlin
force-pushed
the
topic/add-techdocs-action
branch
from
8572c9e
to
d91c639
Compare
Signed-off-by: Andre Wanlin <[email protected]>
freben
approved these changes
Nov 23, 2023
agentbellnorm
approved these changes
Nov 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a workflow that runs daily at 10:00am UTC to publish the Backstage TechDocs to the GCS bucket and then can be displayed in the Demo site.
Currently this is not happening and the content is very stale. Keeping this up to date will provide a better "demo", give us a place to validate releases, and stay in sync with the actual documentation.
Note: I will need some support with this as I don't have access to the needed secret or anything on the GCS side