From 1fd8c2e7b38b047f1b4681bf8d8a04635f36c475 Mon Sep 17 00:00:00 2001
From: Konstantin Shurukhin List of file system paths to ignore when detecting changes in the project(s). The primary purpose is to skip creating new releases if only "infrastructure" files such as
+ * .gitignore, .editorconfig and the like changed. Very basic wild cards are supported as
+ * follows:
+ *
+ *
/foo.txt - matches foo.txt in the root of the top-level project/bar/foo.txt - matches foo.txt in the root of the bar directory that resides in the root of the top-level project/bar/ - matches the bar directory and it's contents in the root of the top-level projectfoo.txt - matches foo.txt anywhere in the projectbar/foo.txt - matches foo.txt in the bar directory anywhere in the projectbar - matches the bar directory anywhere in the project and ignores everything below
List of file system paths that are required to be changed when detecting changes in the project(s).
+ *The primary purpose is to trigger creating new releases only f certain changes occur in the repository. + * For example, a library repository with ProtoBuf messages would trigger release only if any of the *.proto files has been modified. Very basic wild cards are supported as + * follows: + *
/foo.txt - matches foo.txt in the root of the top-level project/bar/foo.txt - matches foo.txt in the root of the bar directory that resides in the root of the top-level project/bar/ - matches the bar directory and it's contents in the root of the top-level projectfoo.txt - matches foo.txt anywhere in the projectbar/foo.txt - matches foo.txt in the bar directory anywhere in the projectbar - matches the bar directory anywhere in the project and ignores everything belowExcludes the ignoredPaths logic
List of file system paths that are required to be changed when detecting changes in the project(s).
- *The primary purpose is to trigger creating new releases only f certain changes occur in the repository. + *
If not set, any change triggers the release logic.
+ *The primary purpose is to trigger creating new releases only if certain changes occur in the repository. * For example, a library repository with ProtoBuf messages would trigger release only if any of the *.proto files has been modified. Very basic wild cards are supported as * follows: *