-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
4 additions
and
44 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1,8 @@ | ||
checks: | ||
- specification | ||
- branch-has-specification | ||
- allowed-project | ||
- branch-release | ||
- codevalidator | ||
specification: | ||
format: 'jira' | ||
branch-has-specification: | ||
exceptions: | ||
- '^release/' | ||
allowed-project: | ||
allowed: | ||
- PF | ||
- CD | ||
branch-release: | ||
pattern: '^v(?:\d|\_|\.)+$' |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,24 +1,7 @@ | ||
Commit Specification | ||
==================== | ||
|
||
Overview | ||
-------- | ||
Commit specifications are urlencoded uniform resource identifiers (URI). The specification must be the first “word” of | ||
the commit and can optionally start with a ‘#’ character that is ignored. For readability purposes the scheme of the | ||
specification URI can be omitted if the same as the default for the repository. | ||
|
||
|
||
Schemes | ||
------- | ||
### Generic | ||
Generic specification without a special meaning. Generic specifications are always valid. | ||
This format is used by default if scheme is missing from the URI and there is no default scheme for the repository. | ||
|
||
### JIRA | ||
JIRA specification URIs take the form of “jira:PROJECT-TICKET_NUMBER” for example “jira:CD-123” | ||
|
||
### Github | ||
Github specifications URIs take the form of “github:ISSUE_NUMBER” where ISSUE_NUMBER is the number of the specification | ||
on the repository | ||
|
||
### HTTP(S) | ||
Specifications can also be http and https urls. | ||
Commit specifications are urlencoded absolute uniform resource identifiers (URI). The specification must be the first | ||
“word” of the commit. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters