chore(ci): Generate code and docs for dependencies updates#3346
chore(ci): Generate code and docs for dependencies updates#3346kodiakhq[bot] merged 2 commits intocloudquery:mainfrom
Conversation
| // e.g. plugins/source/aws/go.mod | ||
| const plugin = goModFile.split('/')[2] | ||
| console.log({ issue_number, owner, repo, sha, plugin }); | ||
| await github.rest.issues.createComment({ |
There was a problem hiding this comment.
This comment triggers the /gen command for this plugin (to re-use that workflow)
|
Can we just rigger this the same way as we do with docs and linters and see if anything changed ? |
If we do that, then as soon as package update is released then the next pr will have to update (even if it is for a completely different resource) |
I think that would make our workflows a bit complex, see just AWS https://github.com/cloudquery/cloudquery/compare/main...erezrokah:chore/update_code_docs_prs?expand=1 And this is also missing the check for branch name logic. The complexity comes from needing to use a personal access token otherwise the new commit won't trigger the CI (built in GitHub token limitation). So we need to support both forked workflows (where we can't use an elevated token) and a non forked workflows |
Summary
Fixes #3326, to be merged after #3345.
Based on https://github.com/cloudquery/helm-charts/blob/8b1b9b5ece94a92e1ac329594645a4b3318a9c4d/.github/workflows/deps_bump_versions.yml