diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestApprovedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestApprovedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestApprovedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestApprovedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentCreatedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentCreatedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentCreatedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentCreatedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentDeletedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentDeletedActionFilter/help-allowed.html
index 7c39aee1..ee06a69b 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentDeletedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentDeletedActionFilter/help-allowed.html
@@ -2,12 +2,8 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
+
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +12,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentUpdatedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentUpdatedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentUpdatedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCommentUpdatedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCreatedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCreatedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCreatedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestCreatedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestDeclinedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestDeclinedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestDeclinedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestDeclinedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestMergedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestMergedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestMergedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestMergedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestUpdatedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestUpdatedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestUpdatedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/cloud/BitBucketPPRPullRequestUpdatedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerApprovedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerApprovedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerApprovedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerApprovedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerCommentCreatedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerCommentCreatedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerCommentCreatedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerCommentCreatedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerCreatedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerCreatedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerCreatedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerCreatedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerDeclinedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerDeclinedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerDeclinedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerDeclinedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerMergedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerMergedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerMergedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerMergedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerSourceUpdatedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerSourceUpdatedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerSourceUpdatedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerSourceUpdatedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerUpdatedActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerUpdatedActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerUpdatedActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/pullrequest/server/BitBucketPPRPullRequestServerUpdatedActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/repository/BitBucketPPRRepositoryPushActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/repository/BitBucketPPRRepositoryPushActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/repository/BitBucketPPRRepositoryPushActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/repository/BitBucketPPRRepositoryPushActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.
diff --git a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/repository/BitBucketPPRServerRepositoryPushActionFilter/help-allowed.html b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/repository/BitBucketPPRServerRepositoryPushActionFilter/help-allowed.html
index 7c39aee1..08be6bf1 100644
--- a/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/repository/BitBucketPPRServerRepositoryPushActionFilter/help-allowed.html
+++ b/src/main/resources/io/jenkins/plugins/bitbucketpushandpullrequest/filter/repository/BitBucketPPRServerRepositoryPushActionFilter/help-allowed.html
@@ -2,12 +2,6 @@
Specify the branches if you'd like to track a specific branch in a repository.
If left blank, all branches will be examined for changes and built.
- The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch
- is unambiguous.
-
- If your branch name has a / in it make sure to use the full reference above. When not presented
- with a full path the plugin will only use the part of the string right of the last slash.
- Meaning foo/bar will actually match bar.
If you use a wildcard branch specifier, with a slash (e.g. release/),
you'll need to specify the origin repository in the branch names to
@@ -16,14 +10,10 @@
Possible options:
-
<branchName>
- Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
- the expected one. Better use refs/heads/<branchName>.
+ Tracks/checks out the specified branch.
E.g. master, feature1, ...
- -
refs/heads/<branchName>
- Tracks/checks out the specified branch.
- E.g. refs/heads/master, refs/heads/feature1/master, ...
-
+
-
<remoteRepoName>/<branchName>
Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily
the expected one.