Skip to content

Conversation

@amoeba
Copy link
Contributor

@amoeba amoeba commented Jan 6, 2026

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

@amoeba amoeba requested a review from lidavidm as a code owner January 6, 2026 22:41
@amoeba
Copy link
Contributor Author

amoeba commented Jan 6, 2026

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 --dry-run in https://github.com/amoeba/databricks/actions/runs/20764451655/job/59627289506.

Copy link
Contributor

@lidavidm lidavidm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 <li.davidm96@gmail.com>
@lidavidm lidavidm merged commit 226de83 into adbc-drivers:main Jan 20, 2026
3 checks passed
@amoeba
Copy link
Contributor Author

amoeba commented Jan 20, 2026

Thanks for merging. I was in the middle of debugging a failure I ran into while testing but had to start making dinner. I got this permissions error in https://github.com/amoeba/databricks/actions/runs/20764451655/job/60843093924 that made me think for some reason you can't update workflows from workflows but it worked before during testing so I'm probably just tired.

Maybe just keep that in mind when we put it in place.

@lidavidm
Copy link
Contributor

Oh huh. I think I remember seeing stuff like that before. We just have to add that permission to the list.

@amoeba
Copy link
Contributor Author

amoeba commented Jan 20, 2026

You'd think but, unless I'm doing something wrong, you can't add workflow to permissions since it isn't on the list. My LSP errors and it looks like github rejects the entire workflow file as invalid before starting the job.

@lidavidm
Copy link
Contributor

Ugh. I guess they've changed this around. It seems we have to give the workflow access to a token for this specific purpose.

@lidavidm
Copy link
Contributor

I'm not sure this really saves us all that much time anymore then...at least, we'd need to be watching for and rotating tokens for each repo which is itself a pain

@lidavidm
Copy link
Contributor

Or we need to explicitly make a GitHub App which can be granted the permissions

@amoeba
Copy link
Contributor Author

amoeba commented Jan 20, 2026

Yeah. I almost submitted a PR to at least avoid the workflow write issue with this commit: amoeba@bcc5e73 but I need to test to confirm this is what I think is going on (tomorrow).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants