From 45c3e5fe5bb64a50baed174a64df3762c02b6315 Mon Sep 17 00:00:00 2001
From: Hans Christian Winther-Sorensen <hc@wsh.no>
Date: Thu, 10 Oct 2024 14:33:02 +0200
Subject: [PATCH] Bugfix/TEST-0007-restore-inspect-code (#298)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!--- Provide a general summary of your changes in the Title above -->

## Description 💬
<!--- Describe your changes in detail -->

## Motivation and Context 🥅
<!--- Why is this change required? What problem does it solve? -->
<!--- If it fixes an open issue, please link to the issue here. -->

## How has this been tested? 🧪
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, tests ran to see how
-->
<!--- your change affects other areas of the code, etc. -->
- [ ] Local build ⚒️
- [ ] Local tests 🧪
- [ ] (optional) Local run and endpoint tested in swagger 🚀

## Screenshots (if appropriate) 💻

## Types of changes 🌊
<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)

## Checklist ☑️

<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
- [ ] The pull request title starts with the jira case number (when
applicable), e.g. "TEST-1234 Add some feature"
- [ ] The person responsible for following up on requested review
changes has been assigned to the pull request
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.

## Highly optional checks, only use these if you have a reason to do so
✔️

- [ ] This PR changes the database so I have added the *create-diagram*
label to assist reviewers with a db diagram
- [ ] This PR changes platform or backend and I need others to be able
to test against these changes before merging to dev, so I have added the
*deploy-azure* label to deploy before merging the PR

## Checklist for the approver ✅

- [ ] I've checked the files view for spelling issues, code quality
warnings and similar
- [ ] I've waited until all checks have passed (green check/without
error)
- [ ] I've checked that only the intended files are changed
---
 .github/workflows/backend-ci.yml | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/.github/workflows/backend-ci.yml b/.github/workflows/backend-ci.yml
index 552fd6ed..b59e9510 100644
--- a/.github/workflows/backend-ci.yml
+++ b/.github/workflows/backend-ci.yml
@@ -218,15 +218,15 @@ jobs:
           comment-identifier: "${{ env.WORKFLOW_SHORT_NAME }}-Stryker"
           comment-content: ${{ steps.stryker.outputs.markdown }}
 
-      # - name: Inspect code
-      #   uses: muno92/resharper_inspectcode@v1
-      #   if: ${{ github.event_name == 'pull_request' }}
-      #   with:
-      #     workingDirectory: ${{ env.BACKEND_SOLUTION_PATH }}
-      #     solutionPath: Backend.sln
-      #     dotnetVersion: ${{ env.DOTNET_VERSION }}
-      #     failOnIssue: false
-      #     solutionWideAnalysis: true
-      #     include: |
-      #       **.cs
-      #     ignoreIssueType: PropertyCanBeMadeInitOnly.Global
+      - name: Inspect code
+        uses: muno92/resharper_inspectcode@v1
+        if: ${{ github.event_name == 'pull_request' }}
+        with:
+          workingDirectory: ${{ env.BACKEND_SOLUTION_PATH }}
+          solutionPath: Backend.sln
+          dotnetVersion: ${{ env.DOTNET_VERSION }}
+          failOnIssue: false
+          solutionWideAnalysis: true
+          include: |
+            **.cs
+          ignoreIssueType: PropertyCanBeMadeInitOnly.Global