mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 14:56:05 +00:00
gcloud: Wed Mar 1 10:23:17 UTC 2023
This commit is contained in:
parent
7664984b79
commit
bdaa0b3cfc
230 changed files with 8963 additions and 242 deletions
|
|
@ -128,9 +128,10 @@ REQUIRED FLAGS
|
|||
--branch-pattern=REGEX
|
||||
A regular expression specifying which git branches to match.
|
||||
|
||||
This pattern is used as a regex search for any incoming pushes.
|
||||
For example, --branch-pattern=foo will match "foo", "foobar", and
|
||||
"barfoo". Events on a branch that does not match will be ignored.
|
||||
This pattern is used as a regular expression search for any
|
||||
incoming pushes. For example, --branch-pattern=foo will match
|
||||
"foo", "foobar", and "barfoo". Events on a branch that does not
|
||||
match will be ignored.
|
||||
|
||||
The syntax of the regular expressions accepted is the syntax
|
||||
accepted by RE2 and described at
|
||||
|
|
@ -139,9 +140,10 @@ REQUIRED FLAGS
|
|||
--tag-pattern=REGEX
|
||||
A regular expression specifying which git tags to match.
|
||||
|
||||
This pattern is used as a regex search for any incoming pushes.
|
||||
For example, --tag-pattern=foo will match "foo", "foobar", and
|
||||
"barfoo". Events on a tag that does not match will be ignored.
|
||||
This pattern is used as a regular expression search for any
|
||||
incoming pushes. For example, --tag-pattern=foo will match "foo",
|
||||
"foobar", and "barfoo". Events on a tag that does not match will
|
||||
be ignored.
|
||||
|
||||
The syntax of the regular expressions accepted is the syntax
|
||||
accepted by RE2 and described at
|
||||
|
|
|
|||
|
|
@ -107,9 +107,10 @@ REQUIRED FLAGS
|
|||
--branch-pattern=REGEX
|
||||
A regular expression specifying which git branches to match.
|
||||
|
||||
This pattern is used as a regex search for any incoming pushes.
|
||||
For example, --branch-pattern=foo will match "foo", "foobar", and
|
||||
"barfoo". Events on a branch that does not match will be ignored.
|
||||
This pattern is used as a regular expression search for any
|
||||
incoming pushes. For example, --branch-pattern=foo will match
|
||||
"foo", "foobar", and "barfoo". Events on a branch that does not
|
||||
match will be ignored.
|
||||
|
||||
The syntax of the regular expressions accepted is the syntax
|
||||
accepted by RE2 and described at
|
||||
|
|
@ -118,9 +119,10 @@ REQUIRED FLAGS
|
|||
--tag-pattern=REGEX
|
||||
A regular expression specifying which git tags to match.
|
||||
|
||||
This pattern is used as a regex search for any incoming pushes.
|
||||
For example, --tag-pattern=foo will match "foo", "foobar", and
|
||||
"barfoo". Events on a tag that does not match will be ignored.
|
||||
This pattern is used as a regular expression search for any
|
||||
incoming pushes. For example, --tag-pattern=foo will match "foo",
|
||||
"foobar", and "barfoo". Events on a tag that does not match will
|
||||
be ignored.
|
||||
|
||||
The syntax of the regular expressions accepted is the syntax
|
||||
accepted by RE2 and described at
|
||||
|
|
|
|||
|
|
@ -119,9 +119,10 @@ REQUIRED FLAGS
|
|||
--branch-pattern=REGEX
|
||||
A regular expression specifying which git branches to match.
|
||||
|
||||
This pattern is used as a regex search for any incoming pushes.
|
||||
For example, --branch-pattern=foo will match "foo", "foobar", and
|
||||
"barfoo". Events on a branch that does not match will be ignored.
|
||||
This pattern is used as a regular expression search for any
|
||||
incoming pushes. For example, --branch-pattern=foo will match
|
||||
"foo", "foobar", and "barfoo". Events on a branch that does not
|
||||
match will be ignored.
|
||||
|
||||
The syntax of the regular expressions accepted is the syntax
|
||||
accepted by RE2 and described at
|
||||
|
|
@ -130,9 +131,10 @@ REQUIRED FLAGS
|
|||
--tag-pattern=REGEX
|
||||
A regular expression specifying which git tags to match.
|
||||
|
||||
This pattern is used as a regex search for any incoming pushes.
|
||||
For example, --tag-pattern=foo will match "foo", "foobar", and
|
||||
"barfoo". Events on a tag that does not match will be ignored.
|
||||
This pattern is used as a regular expression search for any
|
||||
incoming pushes. For example, --tag-pattern=foo will match "foo",
|
||||
"foobar", and "barfoo". Events on a tag that does not match will
|
||||
be ignored.
|
||||
|
||||
The syntax of the regular expressions accepted is the syntax
|
||||
accepted by RE2 and described at
|
||||
|
|
|
|||
|
|
@ -109,9 +109,10 @@ REQUIRED FLAGS
|
|||
--branch-pattern=REGEX
|
||||
A regular expression specifying which git branches to match.
|
||||
|
||||
This pattern is used as a regex search for any incoming pushes.
|
||||
For example, --branch-pattern=foo will match "foo", "foobar", and
|
||||
"barfoo". Events on a branch that does not match will be ignored.
|
||||
This pattern is used as a regular expression search for any
|
||||
incoming pushes. For example, --branch-pattern=foo will match
|
||||
"foo", "foobar", and "barfoo". Events on a branch that does not
|
||||
match will be ignored.
|
||||
|
||||
The syntax of the regular expressions accepted is the syntax
|
||||
accepted by RE2 and described at
|
||||
|
|
@ -120,9 +121,10 @@ REQUIRED FLAGS
|
|||
--tag-pattern=REGEX
|
||||
A regular expression specifying which git tags to match.
|
||||
|
||||
This pattern is used as a regex search for any incoming pushes.
|
||||
For example, --tag-pattern=foo will match "foo", "foobar", and
|
||||
"barfoo". Events on a tag that does not match will be ignored.
|
||||
This pattern is used as a regular expression search for any
|
||||
incoming pushes. For example, --tag-pattern=foo will match "foo",
|
||||
"foobar", and "barfoo". Events on a tag that does not match will
|
||||
be ignored.
|
||||
|
||||
The syntax of the regular expressions accepted is the syntax
|
||||
accepted by RE2 and described at
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue