<type>String</type>
        </field>
        <field xml.transient="true">
          <name>mergeId</name>
          <version>4.0.0</version>
          <description>
            FOR INTERNAL USE ONLY. This is a unique identifier assigned to each
            resource to allow Maven to merge changes to this resource that take
            place during the execution of a plugin. This field must be managed

        final Set<String> merged = new LinkedHashSet<>();

        if (array1 != null) {
            Collections.addAll(merged, array1);
        }

        if (array2 != null) {
            Collections.addAll(merged, array2);
        }

        return merged.toArray(new String[merged.size()]);
    }

    /**
     * Merges two Kind arrays, maintaining uniqueness.
     */

        SuggestItem item2 = createItem("text", 20L, 15L, 2.0f);

        SuggestItem merged = SuggestItemMerger.merge(item1, item2);

        assertNotNull(merged);
        assertEquals(30L, merged.getDocFreq()); // 10 + 20
        assertEquals(20L, merged.getQueryFreq()); // 5 + 15
        assertEquals(2.0f, merged.getUserBoost(), 0.001f); // max(1.0, 2.0)
    }

    @Test
    public void testMerge_tags() {

    }

    /**
     * Merges two suggest items.
     * @param item1 The first suggest item.
     * @param item2 The second suggest item.
     * @return The merged suggest item.
     */
    public static SuggestItem merge(final SuggestItem item1, final SuggestItem item2) {
        return SuggestItemMerger.merge(item1, item2);
    }

    /**

 * but sometimes changes on release notes.md was brought to master and merged unnoticed,
 * e.g https://github.com/gradle/gradle/pull/25825
 *
 * This script is to check if there is any merge commit that brings changes from release branch to master.
 *
 * Usage (Java 11+ single-file source execution):
 *   java .teamcity/scripts/CheckBadMerge.java < commits.txt
 *
 * If any "bad" merge commit is found, it will print the details and exit with non-zero code.

                </details>
                <details>
                  <summary>
                    If change was made on the `release` branch but hasn't yet been merged to `master`, merge `release` to `master`:
                    <span class="btn btn-info" role="button">Merge release to master</span>
                  </summary>
                  <div class="well">

If the tests are passing, you can merge it right away.

## Dependabot PRs

Dependabot will create PRs to update dependencies for several things, and those PRs all look similar, but some are way more delicate than others.

     * Creates an updated source map by merging the item with existing source.
     *
     * @param item The SuggestItem with new data
     * @param existingSource The existing source map from OpenSearch
     * @return A merged source map
     */
    public static Map<String, Object> toUpdatedSource(final SuggestItem item, final Map<String, Object> existingSource) {
        final Map<String, Object> map = new HashMap<>();

things you should know about contributing:

1.  API changes require discussion, use cases, etc. Code comes later.
2.  Pull requests are great for small fixes for bugs, documentation, etc.
3.  Pull requests are not merged directly into the master branch.
4.  Code contributions require signing a Google CLA.

API changes
-----------

We make changes to Guava's public [APIs][], including adding new APIs, very

  @J2ktIncompatible
  @GwtIncompatible // used only in GwtIncompatible tests
  private interface Merger {

    ListenableFuture<List<String>> merged(ListenableFuture<String> a, ListenableFuture<String> b);

    Merger allMerger =
        new Merger() {
          @Override
          public ListenableFuture<List<String>> merged(
              ListenableFuture<String> a, ListenableFuture<String> b) {