Open source the Firebase build tools #7670
Conversation
This is a copy of what was staged and reviewed as of Nov 20, 2025 This does not build yet, I will do that in follow up changes that will: - Add the build tools modules to the subprojects.cfg file - Reformat according to the new formatting rules - Fix any small failures so everything builds and tests pass - Migrate the workflows - Pull in any changes since Nov 20 Turbo: 543201
This adds the build tools modules to the subprojects.cfg file, fixes some formatting issues with markdown files, and cleans up error prone failures
This is missing from #7658
This pulls in all the changes since Nov 20, when the build tools source was staged for open source
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
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Using Gemini Code AssistThe 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
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 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. |
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
Explicitly set permissions: contents: read only Based on warning from https://github.com/firebase/firebase-android-sdk/security/code-scanning/469
3 participants
See main...feature/openSourceBuildTools for the details
Feature for: