feat: create dev_daily workflow to sync workflows #42
Conversation
|
Hey @lidavidm, i thought about #30 today and came up with this. The reason I went this route was to work around any auth issues. Creating a true bot would require a PAT or a full-blown GitHub App, or at least I think it would. This works around that by placing the workflow in each repo. Thoughts? I ran a test of the workflow with |
| --base main \ | ||
| --head $BRANCH \ | ||
| --title "$PR_TITLE" \ | ||
| --body "TODO" \ |
There was a problem hiding this comment.
Will fix this before merge.
| --head $BRANCH \ | ||
| --title "$PR_TITLE" \ | ||
| --body "TODO" \ | ||
| --dry-run |
There was a problem hiding this comment.
Will remove this before merge.
lidavidm
left a comment
lidavidm
left a comment
There was a problem hiding this comment.
This is a great idea!
I think we may also need to fix the templates, e.g. for pixi.toml, some test suites have more dependencies (pytest-lazy-fixtures in particular)
Co-authored-by: David Li <[email protected]>
2 participants
What's Changed
Creates a generated workflow we can add to driver repos which keeps them up to date with any workflow updates in this repo. The workflow runs daily and creates a PR if adbc-gen-workflow generate modified any files.
Ref #30