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
So they do not need to be specified every invocation:
218
+
219
+
```shell
220
+
act pull_request
221
+
```
222
+
223
+
To test the `ci-go/terraform-provider-corner` job, a valid GitHub Personal Access Token (PAT) with public read permissions is required. It can be passed in via the `-s GITHUB_TOKEN=...` command option.
224
+
225
+
### Go Unit Tests
226
+
227
+
Go code unit testing is perfomed via Go's built-in testing functionality.
228
+
229
+
To run the Go unit testing locally:
230
+
231
+
```shell
232
+
go test ./...
233
+
```
182
234
183
235
This codebase follows Go conventions for unit testing. Some guidelines include:
184
236
@@ -263,6 +315,16 @@ Run the [`changelog-build`](https://pkg.go.dev/github.com/hashicorp/go-changelog
This will generate a section of Markdown text for the next release. Open the `CHANGELOG.md` file, add a `# X.Y.Z (Unreleased)` header as the first line, then add the output from the `changelog-build` command. The `(Unreleased)` suffix after the version number is required for the current release process.
318
+
This will generate a section of Markdown text for the next release. Open the `CHANGELOG.md` file, add a `# X.Y.Z` header as the first line, then add the output from the `changelog-build` command.
319
+
320
+
Commit, push, create a release Git tag, and push the tag:
321
+
322
+
```shell
323
+
git add CHANGELOG.md
324
+
git commit -m "Update CHANGELOG for v1.2.3"
325
+
git push
326
+
git tag v1.2.3
327
+
git push --tags
328
+
```
267
329
268
-
Refer to the HashiCorp internal Engineering documentation for information about completing the release process once the changelog has been prepared.
330
+
GitHub Actions will pick up the new release tag and kick off the release workflow.
0 commit comments