Rename dockers directory to tool #3495
Conversation
|
A Kapetanios build has just been triggered to run docker operations for the following
|
|
The following files are not gofmt-ed. By commenting tool/actions/gh/release/comment_test.go--- tool/actions-gh-release/comment_test.go.orig
+++ tool/actions-gh-release/comment_test.go
@@ -35,7 +35,7 @@
{
name: "one release",
proposals: []ReleaseProposal{
- ReleaseProposal{
+ {
ReleaseNote: "Release note for tag 1",
},
},
@@ -44,10 +44,10 @@
{
name: "multiple releases",
proposals: []ReleaseProposal{
- ReleaseProposal{
+ {
ReleaseNote: "Release note for tag 1",
},
- ReleaseProposal{
+ {
ReleaseNote: "Release note for tag 2",
},
},
tool/actions/gh/release/release_test.go--- tool/actions-gh-release/release_test.go.orig
+++ tool/actions-gh-release/release_test.go
@@ -52,28 +52,28 @@
},
},
CommitCategories: []ReleaseCommitCategoryConfig{
- ReleaseCommitCategoryConfig{
+ {
ID: "_category_0",
Title: "Breaking Changes",
ReleaseCommitMatcherConfig: ReleaseCommitMatcherConfig{
Contains: []string{"change-category/breaking-change"},
},
},
- ReleaseCommitCategoryConfig{
+ {
ID: "_category_1",
Title: "New Features",
ReleaseCommitMatcherConfig: ReleaseCommitMatcherConfig{
Contains: []string{"change-category/new-feature"},
},
},
- ReleaseCommitCategoryConfig{
+ {
ID: "_category_2",
Title: "Notable Changes",
ReleaseCommitMatcherConfig: ReleaseCommitMatcherConfig{
Contains: []string{"change-category/notable-change"},
},
},
- ReleaseCommitCategoryConfig{
+ {
ID: "_category_3",
Title: "Internal Changes",
ReleaseCommitMatcherConfig: ReleaseCommitMatcherConfig{},
@@ -115,28 +115,28 @@
},
},
CommitCategories: []ReleaseCommitCategoryConfig{
- ReleaseCommitCategoryConfig{
+ {
ID: "breaking-change",
Title: "Breaking Changes",
ReleaseCommitMatcherConfig: ReleaseCommitMatcherConfig{
Contains: []string{"change-category/breaking-change"},
},
},
- ReleaseCommitCategoryConfig{
+ {
ID: "new-feature",
Title: "New Features",
ReleaseCommitMatcherConfig: ReleaseCommitMatcherConfig{
Contains: []string{"change-category/new-feature"},
},
},
- ReleaseCommitCategoryConfig{
+ {
ID: "notable-change",
Title: "Notable Changes",
ReleaseCommitMatcherConfig: ReleaseCommitMatcherConfig{
Contains: []string{"change-category/notable-change"},
},
},
- ReleaseCommitCategoryConfig{
+ {
ID: "internal-change",
Title: "Internal Changes",
ReleaseCommitMatcherConfig: ReleaseCommitMatcherConfig{},
@@ -163,30 +163,30 @@
{
name: "ok",
commits: []Commit{
- Commit{
+ {
Subject: "Commit 1 message",
Body: "commit 1\napp/hello\n- change-category/breaking-change",
},
- Commit{
+ {
Subject: "Commit 2 message",
Body: "commit 2\napp/hello",
},
- Commit{
+ {
Subject: "Commit 3 message",
Body: "commit 3\napp/hello\n- change-category/notable-change",
},
- Commit{
+ {
Subject: "Commit 4 message",
Body: "commit 4\napp/hello\n```release-note\nCommit 4 release note\n```\n- change-category/notable-change\n",
},
- Commit{
+ {
Subject: "Commit 5 message",
Body: "commit 5",
},
},
config: config,
expected: []ReleaseCommit{
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 1 message",
Body: "commit 1\napp/hello\n- change-category/breaking-change",
@@ -194,7 +194,7 @@
CategoryName: "breaking-change",
ReleaseNote: "Commit 1 message",
},
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 2 message",
Body: "commit 2\napp/hello",
@@ -202,7 +202,7 @@
CategoryName: "internal-change",
ReleaseNote: "Commit 2 message",
},
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 3 message",
Body: "commit 3\napp/hello\n- change-category/notable-change",
@@ -210,7 +210,7 @@
CategoryName: "notable-change",
ReleaseNote: "Commit 3 message",
},
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 4 message",
Body: "commit 4\napp/hello\n```release-note\nCommit 4 release note\n```\n- change-category/notable-change\n",
@@ -317,28 +317,28 @@
Tag: "v0.2.0",
PreTag: "v0.1.0",
Commits: []ReleaseCommit{
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 1 message",
Body: "commit 1\n- change-category/breaking-change",
},
ReleaseNote: "Commit 1 message",
},
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 2 message",
Body: "commit 2",
},
ReleaseNote: "Commit 2 message",
},
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 3 message",
Body: "commit 3\n- change-category/notable-change",
},
ReleaseNote: "Commit 3 message",
},
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 4 message",
Body: "commit 4\n```release-note\nCommit 4 release note\n```\n- change-category/notable-change",
@@ -356,7 +356,7 @@
Tag: "v0.2.0",
PreTag: "v0.1.0",
Commits: []ReleaseCommit{
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 1 message",
Body: "commit 1\n- change-category/breaking-change",
@@ -364,7 +364,7 @@
CategoryName: "breaking-change",
ReleaseNote: "Commit 1 message",
},
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 2 message",
Body: "commit 2",
@@ -372,7 +372,7 @@
CategoryName: "internal-change",
ReleaseNote: "Commit 2 message",
},
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 3 message",
Body: "commit 3\n- change-category/notable-change",
@@ -380,7 +380,7 @@
CategoryName: "notable-change",
ReleaseNote: "Commit 3 message",
},
- ReleaseCommit{
+ {
Commit: Commit{
Subject: "Commit 4 message",
Body: "commit 4\n```release-note\nCommit 4 release note\n```\n- change-category/notable-change",
@@ -392,19 +392,19 @@
},
config: ReleaseConfig{
CommitCategories: []ReleaseCommitCategoryConfig{
- ReleaseCommitCategoryConfig{
+ {
ID: "breaking-change",
Title: "Breaking Changes",
},
- ReleaseCommitCategoryConfig{
+ {
ID: "new-feature",
Title: "New Features",
},
- ReleaseCommitCategoryConfig{
+ {
ID: "notable-change",
Title: "Notable Changes",
},
- ReleaseCommitCategoryConfig{
+ {
ID: "internal-change",
Title: "Internal Changes",
},
|
|
The Kapetanios build to run docker operations for the following 1. tool/actions-plan-preview - successAn image named actions-plan-preview:1.7.2-8f60d48 was procuded for reviewing and testing. There is no test to run inside this directory. 2. tool/actions-gh-release - successAn image named actions-gh-release:2.3.4-8f60d48 was procuded for reviewing and testing. There is no test to run inside this directory. |
|
A Kapetanios build has just been triggered to run docker operations for the following
|
|
A Kapetanios build has just been triggered to run docker operations for the following
|
|
The Kapetanios build to run docker operations for the following 1. tool/actions-gh-release - scheduledAn image named actions-gh-release:2.3.4-af1c965 was procuded for reviewing and testing. There is no test to run inside this directory. |
|
The golinter build is completed with FAILURE. The build will be triggered again when you push any other commits. Or you can trigger it manually by You can check the build log from here. |
|
The Kapetanios build to run docker operations for the following 1. tool/actions-gh-release - successAn image named actions-gh-release:2.3.4-ec409da was procuded for reviewing and testing. There is no test to run inside this directory. |
|
Nice |
|
Code coverage for golang is |
|
Here you go |
|
This pull request is APPROVED by Approvers can cancel the approval by writing |
**What this PR does / why we need it**: https://pipecd.dev/docs/user-guide/configuration-reference/#kubernetesdeploymentinput **Which issue(s) this PR fixes**: Fixes #3495 **Does this PR introduce a user-facing change?**: ```release-note NONE ``` This PR was merged by Kapetanios.
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: