Replace test.yaml

sergerad · Nov 23, 2023 · f78bd02 · f78bd02
1 parent 9d556e0
commit f78bd02
Show file tree

Hide file tree

Showing 3 changed files with 11 additions and 39 deletions.
diff --git a/.github/workflows/coverage.yaml → .github/workflows/pr.yaml b/.github/workflows/coverage.yaml → .github/workflows/pr.yaml
@@ -1,4 +1,4 @@
-name: Generate code coverage badge
+name: Test src and generate coverage badge
 
 on:
   pull_request:
@@ -21,6 +21,14 @@ jobs:
         with:
           go-version-file: 'go.mod'
 
+      - name: Run lint
+        uses: golangci/golangci-lint-action@v3
+        with:
+          version: v1.55
+
+      - name: Go build
+        run: go build -v ./...
+
       - name: Run Test
         run: |
           go test -v ./... -covermode=count -coverprofile=coverage.out

diff --git a/.github/workflows/test.yaml b/.github/workflows/test.yaml
diff --git a/README.md b/README.md
@@ -1,7 +1,8 @@
 # Relax
-![Coverage](https://img.shields.io/badge/Coverage-100.0%25-brightgreen)
 #### *...there's no need to panic.*
 
+![Coverage](https://img.shields.io/badge/Coverage-100.0%25-brightgreen)
+
 In some situations, encountering a panic can be problematic. For example:
 * If your REST server panics while handling a POST request, you may end up with a dangling resource in your database;
 * Applications that write state to filesystems may produce irrecoverable state if a series of dependant file writes is interrupted by a panic; and