Skip to content

Conversation

@mrober
Copy link
Contributor

@mrober mrober commented Jan 21, 2026

This copies over the workflows from the old build tools repo

I did some modifications to make it more consistent with the rest of this repo. The names are modified to match the rest of this repo. Also removed the custom setup env action and manually do the setup in each action since the rest of the workflows here do that. I also removed all the soft versions on uses like @v3 and replaced them with specific commit hashes used in other workflows

Tested the gradle compatibility test by temporarily triggering it on PR
Could not test the make releases workflow because I can't get it to show up in Actions, will test after merging

We don't need to copy the unit tests workflow because the CI Tests are smart and catches the new modules when they have changes

@gemini-code-assist
Copy link
Contributor

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

@mrober mrober force-pushed the mrober/buildToolsWorkFlows branch 2 times, most recently from 5691deb to 9fd5232 Compare January 21, 2026 17:09
@mrober mrober requested review from rlazo and themiswang January 21, 2026 17:09
Copy link
Contributor

@themiswang themiswang left a comment

Choose a reason for hiding this comment

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

Seems like build release cannot run on non-default branch, approve for merging
https://github.com/orgs/community/discussions/172914

@mrober mrober requested a review from davidmotson January 21, 2026 19:12
Copy link
Collaborator

@rlazo rlazo left a comment

Choose a reason for hiding this comment

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

Since the comment is for a name change, I approve it as to not block it.

@mrober mrober force-pushed the mrober/buildToolsLatestChanges branch from 77ec48a to 479178c Compare January 21, 2026 21:42
@mrober mrober force-pushed the mrober/buildToolsWorkFlows branch from 18efca2 to c83787c Compare January 21, 2026 21:48
@mrober mrober force-pushed the mrober/buildToolsLatestChanges branch 2 times, most recently from 523acbf to 14dfe28 Compare January 22, 2026 15:09
@mrober mrober force-pushed the mrober/buildToolsWorkFlows branch from f4f07b5 to f2b16ec Compare January 22, 2026 15:19
@mrober mrober changed the base branch from mrober/buildToolsLatestChanges to feature/openSourceBuildTools January 22, 2026 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants