You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-20Lines changed: 8 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ There are two main components:
11
11
- Forward Kinesis data stream events to Datadog, only CloudWatch logs are supported
12
12
- Forward custom metrics from AWS Lambda functions via CloudWatch logs
13
13
- Forward traces from AWS Lambda functions via CloudWatch logs
14
-
- Generate and submit enhanced Lambda metrics (aws.lambda.enhanced.*) parsed from the AWS REPORT log: duration, billed_duration, max_memory_used, and estimated_cost
14
+
- Generate and submit enhanced Lambda metrics (`aws.lambda.enhanced.*`) parsed from the AWS REPORT log: duration, billed_duration, max_memory_used, and estimated_cost
15
15
16
16
17
17
## Usage
@@ -66,35 +66,23 @@ Cloudwatch log sync are namspaced by module.
Releases are cut using [go-semrel-gitlab](https://gitlab.com/juhani/go-semrel-gitlab)
75
+
Releases are cut using [semantic-release](https://github.com/semantic-release/semantic-release).
76
76
77
-
Format commit messages using [Conventional Commits format](https://www.conventionalcommits.org/en/v1.0.0-beta.2/) to determine the next version bump and to produce release notes
77
+
Please write commit messages following [Angular commit guidelines](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines)
78
78
79
-
```
80
-
type(scope): subject
81
-
```
82
-
or
83
79
84
-
```
85
-
type: subject
86
-
```
87
-
88
-
Types:
89
-
```
90
-
minor bump: feat
91
-
patch bump: fix,refactor,perf,docs,style,tes
92
-
```
80
+
### Release flow
93
81
94
-
When a commit contains a breaking change, the commit message should contain `BREAKING CHANGE:`
82
+
Semantic-release is configured with the [default branch workflow](https://semantic-release.gitbook.io/semantic-release/usage/configuration#branches)
95
83
84
+
For this project, releases will be cut from master as features and bugs are developed.
0 commit comments