1.  Make sure the Issue Template is filled out.
1.  The issue should be related to the repo it is created in.

**Here's why we have this policy:** We want to focus on the work that benefits
the whole community, e.g., fixing bugs and adding features. Individual support
should be sought on Stack Overflow or other non-GitHub channels. It helps us to

  }

  /** Test equalObjects after adding multiple instances at once with a null */
  public void testAddTwoEqualObjectsAtOnceWithNull() {
    assertThrows(
        NullPointerException.class,
        () -> equalsTester.addEqualityGroup(reference, equalObject1, null));
  }

  /** Test adding null equal object yields error */
  public void testAddNullEqualObject() {
    assertThrows(

        project.getPluginManager().apply(LoggerUsagePrecommitPlugin.class);
        project.getPluginManager().apply(JarHellPrecommitPlugin.class);

        // tasks with just tests don't need certain tasks to run, so this flag makes adding
        // the task optional
        if (withProductiveCode) {
            project.getPluginManager().apply(ThirdPartyAuditPrecommitPlugin.class);

<% for (version in changelogsByVersionByTypeByArea.keySet()) {
def unqualifiedVersion = version.withoutQualifier()
%>[[release-notes-$unqualifiedVersion]]
== {es} version ${unqualifiedVersion}
<% if (version.isSnapshot()) { %>
coming[$unqualifiedVersion]
<% } %>
Also see <<breaking-changes-${ version.major }.${ version.minor },Breaking changes in ${ version.major }.${ version.minor }>>.
<% if (changelogsByVersionByTypeByArea[version]["security"] != null) { %>

    * This is for security fixes, like vulnerabilities. It would almost never be used.
* `feature`: Features
    * New features, adding support for things that didn't exist before.
* `bug`: Fixes

    @Test
    public void test_fromClassNameToComponentName() {
        // Test with class name ending with Pager
        String componentName = namingConvention.fromClassNameToComponentName("com.example.TestPager");
        assertNotNull(componentName);
        assertEquals("testPager", componentName);

        // Test with class name not ending with Pager

import org.gradle.api.Plugin;
import org.gradle.api.Project;
import org.gradle.api.Task;
import org.gradle.api.plugins.JavaPluginExtension;
import org.gradle.api.tasks.TaskProvider;

/**
 * Base plugin for adding a precommit task.
 */
public abstract class PrecommitPlugin implements Plugin<Project> {

    public static final String PRECOMMIT_TASK_NAME = "precommit";

    @Override
    public final void apply(Project project) {

        // Test with empty strings
        result = jobExecutor.execute("", "");
        assertEquals("Executed:  ", result);
    }

    @Test
    public void test_addShutdownListener() {
        // Test adding shutdown listener
        AtomicBoolean shutdownCalled = new AtomicBoolean(false);
        ShutdownListener listener = new ShutdownListener() {
            @Override
            public void onShutdown() {

 *   <li>{@code Client} - The client used for accessing the settings.</li>
 * </ul>
 *
 * <p>Logging:</p>
 * <ul>
 *   <li>Uses {@code Logger} to log debug information when adding, deleting, or deleting all elevate words.</li>
 * </ul>
 */
public class ElevateWordSettings {
    private static final Logger logger = LogManager.getLogger(ElevateWordSettings.class);

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see