feat: organize gha workflow files

[ncooke3]

Summary
This PR reorganizes the .github/workflows directory to improve scannability and maintainability. Previously, the flat structure mixed product CI, infrastructure tools, and release trains, making it difficult to find and group related workflows.

The .github/workflows directory is more organized and now consistently structured: https://github.com/firebase/firebase-ios-sdk/tree/nc/org-gha/.github/workflows

The list on right-side of page here will be easier to scan: https://github.com/firebase/firebase-ios-sdk/actions

I have adopted a new naming convention to logically group files by their domain.

Convention

• sdk.*: Core product CI and Nightly jobs.

  • Benefit: Groups main CI and scheduled variants together (e.g., sdk.firestore.yml now sits next to sdk.firestore.nightly.yml).
  • Change: Replaces ad-hoc naming.

• infra.*: Repository-level maintenance, global checks, and sample apps.

  • Examples: infra.check.yml, infra.danger.yml, infra.samples.watchos.yml.

• release.*: Release engineering, explicitly grouped by distribution channel (SPM, CocoaPods, Zip).

  • Examples: release.spm.yml, release.cocoapods.prerelease.yml.

• _ (Underscore): Reusable workflows and templates.

  • Benefit: Forces internal "library" files to the top of the sort order for easy distinction.
  • Change: Replaces common_ prefixes.

Process

• Renamed all workflow files to match the new schema.
• Updated all internal uses: references for reusable workflows.
• Updated self-referential paths: triggers to match new filenames.
• No logic changes were made to the workflow steps themselves.

#no-changelog

[gemini-code-assist]

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.