# See https://pre-commit.com for more information
# See https://pre-commit.com/hooks.html for more hooks
repos:
  - repo: https://github.com/pre-commit/pre-commit-hooks
    rev: v6.0.0
    hooks:
      - id: check-added-large-files
        args: ['--maxkb=750']
        exclude: ^uv.lock$
      - id: check-toml
      - id: check-yaml
        args:
        - --unsafe
      - id: end-of-file-fixer
      - id: trailing-whitespace

          if git diff --staged --quiet; then
            echo "No changes to commit"
          else
            git commit -m "🎨 Auto format"
            git push
          fi
      - uses: pre-commit-ci/lite-action@v1.1.0
        if: env.HAS_SECRETS == 'false'
        with:
          msg: 🎨 Auto format
      - name: Error out on pre-commit errors
        if: steps.precommit.outcome == 'failure'
        run: exit 1

    private static void checkCommit(String commit) throws IOException, InterruptedException, ExecutionException {
        List<String> parentCommits = parentCommitsOf(commit);
        if (parentCommits.size() != 2) {
            System.out.println(commit + " is not a merge commit we're looking for. Parents: " + parentCommits);
            return;
        }

        List<String> commitBranches = branchesOf(commit);

            System.out.println("Commit " + commit + " wrapper: " + wrapperVersion);
            if (!ALLOWED_WRAPPER_VERSION.matcher(wrapperVersion).matches()) {
                System.err.println(
                    "Bad wrapper version " + wrapperVersion + " used in commit " + commit
                        + ". Please rebase your branch to ensure that each commit uses only released Gradle versions in wrapper (GA, RC or milestone)."

        // Commit
        callback.commit();

        assertEquals(1, commitCount.get());
        assertEquals(3L, documentsBeforeCommit.get());

        // Store more and commit again
        callback.store(params, data);
        callback.store(params, data);

        assertEquals(5L, callback.getDocumentSize());

        callback.commit();

        branch: ${{ github.event.inputs.release_branch }}-${{ steps.cherrypick.outputs.SHORTSHA }}
        reviewers: learning-to-play
        body: |

### Creating commits and writing commit messages

The commit messages that accompany your code changes are an important piece of documentation. Please follow these guidelines when creating commits:

* [Write good commit messages.](https://cbea.ms/git-commit/#seven-rules)

import java.util.stream.Collectors;

/**
 * TeamCity helper script that prints the list of commits in the current PR (one SHA per line).
 *
 * Usage (Java 11+ single-file source execution):
 *   java .teamcity/scripts/FindCommits.java <target_branch_name>
 *
 * Commit range logic:
 * - Uses origin/<target_branch_name> as the target
 * - If HEAD is a merge commit and one parent equals the target SHA, the other parent is treated as PR head

version: 2
updates:
  # GitHub Actions
  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "daily"
    commit-message:
      prefix: ⬆
  # Python
  - package-ecosystem: "uv"
    directory: "/"
    schedule:
      interval: "monthly"
    commit-message:

    to go about it.
2.  All contributions must be licensed Apache 2.0 and all files must have a copy
    of the boilerplate license comment (can be copied from an existing file).
3.  Files should be formatted according to Google's [Java style guide][].
4.  Do your best to have a [well-formed commit message][] for the change.
5.  Pull requests typically do not need to modify the files under the `android`