tag-template: maven-$RESOLVED_VERSION

# Override replacers to strip backport branch prefixes and handle JIRA links
replacers:
  # Strip backport branch prefixes like [maven-4.0.x], [maven-3.x], etc.
  - search: '/^\[maven-[\d\.x-]+\]\s*-?\s*/g'
    replace: ''
  # Convert JIRA ticket references to links (but not maven branch prefixes)
  - search: '/\[([A-Z]+)-(\d+)\]\s*-?\s*/g'

# by a third-party and are governed by separate terms of service, privacy
# policy, and support documentation.

name: Scorecard supply-chain security
on:
  # For Branch-Protection check. Only the default branch is supported. See
  # https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection
  branch_protection_rule:
  # To guarantee Maintained check is occasionally updated. See

### Traduções

- [English](../../README.md)
- [日本語 (Japanese)](../ja/README.md)
- [简体中文 (Simplified Chinese)](../zh-CN/README.md)
- [Español (Spanish)](../es/README.md)
- [Français (French)](../fr/README.md)
- [Deutsch (German)](../de/README.md)
- [한국어 (Korean)](../ko/README.md)

## Desenvolvido por

* [Lasta Di](https://github.com/lastaflute/lasta-di "Lasta Di"): Contêiner DI

```sh
$ cd minio
$ git remote add upstream https://github.com/minio/minio
$ git fetch upstream
$ git merge upstream/master
...
```

### Create your feature branch

Before making code changes, make sure you create a separate branch for these changes

```
git checkout -b my-new-feature
```

### Test MinIO server changes

After your code changes, make sure

    logrotate:
      daysToKeep: 30
      numToKeep: 500
      artifactDaysToKeep: 7
    parameters:
      - string:
          name: branch_specifier
          default: "refs/heads/%BRANCH%"
          description: "the Git branch specifier to build (<branchName>, <tagName>, <commitId>, etc.)\n"
    scm:
      - git:
          name: origin
          # master node jenkins user ~/.ssh

`Field(primary_key=True)` informa ao SQLModel que o `id` é a **chave primária** no banco de dados SQL (você pode aprender mais sobre chaves primárias SQL na documentação do SQLModel).

    **Nota:** Usamos `int | None` para o campo de chave primária para que, no código Python, possamos *criar um objeto sem um `id`* (`id=None`), assumindo que o banco de dados irá *gerá-lo ao salvar*. O SQLModel entende que o banco de dados fornecerá o `id` e *define a coluna como um `INTEGER` não nulo* no esquema...

		</antcall>
		<!-- kopf -->
		<get dest="${target.dir}/kopf.zip">
			<url url="https://github.com/codelibs/fess-kopf/archive/${kopf.branch}.zip" />
		</get>
		<delete dir="${site.dir}/kopf" />
		<unzip dest="${site.dir}/kopf" src="${target.dir}/kopf.zip">
			<patternset>
				<include name="fess-kopf-${kopf.branch}/_site/**" />
			</patternset>
			<cutdirsmapper dirs="2" />
		</unzip>
		<delete>
			<fileset dir="${webinf.dir}/plugin">

      - uses: actions/checkout@v5
        name: Checkout PR for own repo
        if: env.HAS_SECRETS == 'true'
        with:
          # To be able to commit it needs to fetch the head of the branch, not the
          # merge commit
          ref: ${{ github.head_ref }}
          # And it needs the full history to be able to compute diffs
          fetch-depth: 0

   *
   * {@snippet :
   * static final ImmutableGraph<Country> COUNTRY_ADJACENCY_GRAPH =
   *     GraphBuilder.undirected()
   *         .<Country>immutable()
   *         .putEdge(FRANCE, GERMANY)
   *         .putEdge(FRANCE, BELGIUM)
   *         .putEdge(GERMANY, BELGIUM)
   *         .addNode(ICELAND)
   *         .build();
   * }
   *

git checkout main

Development for branch 8x remains in the shared repository:

- https://gitbox.apache.org/repos/asf/lucene-solr.git

## GitHub forks?

If you are using GitHub, make a clone of the corresponding repository
mirror and create your pull requests against the main branch:

- Lucene: <https://github.com/apache/lucene>