Pull requests
-------------

Unless the change is a trivial fix such as for a typo, it's generally best to
start by opening a new issue describing the bug or feature you're intending to
fix. Even if you think it's relatively minor, it's helpful to know what people
are working on. And as mentioned above, API changes should be discussed
thoroughly before moving to code.

Some examples of types of pull requests that are immediately helpful:

        patterns.put("nocommit should be all lowercase or all uppercase", "((?i)nocommit)(?<!(nocommit|NOCOMMIT))");
        patterns.put("tab", "\t");
    }

    @InputFiles
    @PathSensitive(PathSensitivity.RELATIVE)
    @SkipWhenEmpty
    public FileCollection getFiles() {
        return getSourceFolders().get()
            .stream()
            .map(sourceFolder -> sourceFolder.matching(filesFilter))

     * </p>
     * <p>
     * This method is the foundation for {@link SourceRoot#targetPath(Project)} path resolution.
     * When a {@link SourceRoot} has a relative {@code targetPath}, it is resolved against the
     * output directory returned by this method for the source root's scope. This ensures that:
     * </p>
     * <ul>

none;\n}\n\n.popover-body {\n  padding: 0.5rem 0.75rem;\n  color: #212529;\n}\n\n.carousel {\n  position: relative;\n}\n\n.carousel.pointer-event {\n  -ms-touch-action: pan-y;\n  touch-action: pan-y;\n}\n\n.carousel-inner {\n  position: relative;\n  width: 100%;\n  overflow: hidden;\n}\n\n.carousel-inner::after {\n  display: block;\n  clear: both;\n  content: \"\";\n}\n\n.carousel-item {\n  position: relative;\n  display: none;\n  float: left;\n  width: 100%;\n  margin-right: -100%;\n  -webkit-backface-visibility:...

  integTestImplementation "org.xmlunit:xmlunit-core:2.8.2"
}

tasks.register("integTest", Test) {
  inputs.dir(file("src/testKit")).withPropertyName("testkit dir").withPathSensitivity(PathSensitivity.RELATIVE)
  systemProperty 'test.version_under_test', version
  testClassesDirs = sourceSets.integTest.output.classesDirs
  classpath = sourceSets.integTest.runtimeClasspath
  useJUnitPlatform()
}

        byte[] buffer = new byte[120];
        int bufferIndex = 0;

        // Entry 1
        writeInt4(120, buffer, bufferIndex); // nextEntryOffset = 120 (relative)
        writeInt4(1, buffer, bufferIndex + 4); // fileIndex = 1
        writeTime(1672531200000L, buffer, bufferIndex + 8); // creationTime
        writeTime(1672617600000L, buffer, bufferIndex + 24); // lastWriteTime

        problems.setSource("");

        userSettings = interpolate(userSettings, request, problems);

        // for the special case of a drive-relative Windows path, make sure it's absolute to save plugins from trouble
        String localRepository = userSettings.getLocalRepository();
        if (localRepository != null && !localRepository.isEmpty()) {

``` hl_lines="5"
.
├── app
│   ├── __init__.py
│   ├── main.py
│   └── test_main.py
```

Because this file is in the same package, you can use relative imports to import the object `app` from the `main` module (`main.py`):

{* ../../docs_src/app_testing/app_a_py310/test_main.py hl[3] *}


...and have the code for the tests just like before.

    }

    /**
     * Checks if a file exists at the specified path within the servlet context.
     *
     * @param path the file path relative to the servlet context
     * @return true if the file exists, false otherwise
     */
    public static boolean fileExists(final String path) {

    border-bottom: 1px solid #dfe1e6;
}

.card-body.p-0 {
    flex: 1;
    overflow: hidden;
    display: flex;
    flex-direction: column;
    min-height: 0;
    position: relative;
}

/* ============================================
   Empty State (ADS pattern)
   ============================================ */
.empty-state {
    display: flex;
    flex-direction: column;