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
+29-2
Original file line number
Diff line number
Diff line change
@@ -119,16 +119,43 @@ Alternativly you can completly remove the usage of GoReleaser if you prefer hand
119
119
120
120
By default `go test` records code coverage for the package that is currently tested. If you want to get more accurate (cross-package) coverage, then consider using [go-acc](https://github.com/ory/go-acc). [Read more](https://www.ory.sh/golang-go-code-coverage-accurate/).
121
121
122
+
### How to integratee with [Codecov](codecov)
123
+
124
+
1. Sing up on [CodeCov](https://codecov.io/) and setup your repository.
125
+
1. Additionally consider configuring [Codecov GitHub Application](https://github.com/apps/codecov) for better integration.
126
+
1. Add [codecov-action](https://github.com/codecov/codecov-action) to [.github/workflows/build.yml](.github/workflows/build.yml):
There are many possibilites how it can be achieved. Creating release tags manually is often the optimal approach. Take notice that this template executes a release workflow each time a git tag with `v` prefix is pushed.
157
+
However, creating a release tag manually is often the optimal approach. Take notice that this template executes a release workflow each time a git tag with `v` prefix is pushed.
0 commit comments