automate function coverage doc generation #23
Conversation
|
🎊 PR Preview has been successfully built and deployed to https://localstack-snowflake-docs-preview-pr-23.surge.sh 🎊 |
HarshCasper
force-pushed
the
function-doc-automate
branch
from
1de980c to
c6533f7
Compare
| rm -f content/en/references/coverage/index.md && mv index.md content/en/references/coverage/ | ||
|
|
||
| - name: Commit changes | ||
| uses: EndBug/add-and-commit@v9 |
There was a problem hiding this comment.
Is this action pushing the commit straight up to the repo's main branch? I've noticed that in other places we're creating a PR, e.g., for the parity coverage docs: https://github.com/localstack/docs/blob/708939a98c4e2f6732989c139e0dd88b27e2ee8d/.github/workflows/docs-parity-updates.yml#L107 (no strong preference from my side, maybe @yingw787 @ackdav you have some additional thoughts on what would be the best approach here)
There was a problem hiding this comment.
@HarshCasper Looks good to merge from my side - we can see what it feels like for a couple of weeks, and then adjust over time, as needed.. 👍
depends on https://github.com/localstack/snowflake/pull/105