Add optional pre-commit hook for code formatting

.editorconfig

@@ -215,6 +215,7 @@ dotnet_diagnostic.IL2026.severity = none
 dotnet_diagnostic.IL2070.severity = none
 dotnet_diagnostic.IL2075.severity = none
 dotnet_diagnostic.IL2090.severity = none
+dotnet_diagnostic.CA2255.severity = none
 
 # This appears to be broken and results in false positives (causing dotnet format to delete valid test scenarios)
 dotnet_diagnostic.xUnit1025.severity = none

.githooks/pre-commit

@@ -0,0 +1,52 @@
+#!/bin/bash
+set -e
+
+echo "🔍 Checking code formatting..."
+
+STASH_NAME="pre-commit-$(date +%s)"
+
+# Runs on any exit — ensures stashed changes are always restored
+restore_stash() {
+  if git stash list | grep -q "$STASH_NAME"; then
+    git stash pop 2>/dev/null || {
+      echo ""
+      echo "⚠️  Your unstaged changes could not be restored automatically (stash conflict)."
+      echo "   Run 'git stash pop' to restore them manually."
+    }
+  fi
+}
+trap restore_stash EXIT
+
+# Stash unstaged changes (keep staged changes in working tree)
+# This ensures we only check formatting on what's being committed
+git stash push --keep-index --quiet --message "$STASH_NAME" || true
+
+# Run dotnet format (matches CI command exactly)
+dotnet format Sentry.slnx --no-restore \
+  --exclude ./modules ./**/*OptionsSetup.cs ./test/Sentry.Tests/AttributeReaderTests.cs > /dev/null 2>&1
+
+# Check if dotnet format made any changes
+FORMAT_CHANGED=false
+if ! git diff --quiet; then
+  FORMAT_CHANGED=true
+fi
+
+# If formatting changes were detected, fail the commit
+if [ "$FORMAT_CHANGED" = true ]; then
+  echo ""
+  echo "❌ Code formatting issues found!"
+  echo ""
+  echo "Please run the following command to fix formatting:"
+  echo ""
+  echo "  dotnet format Sentry.slnx --no-restore --exclude ./modules ./**/*OptionsSetup.cs ./test/Sentry.Tests/AttributeReaderTests.cs"
+  echo ""
+  echo "Then stage the changes and commit again:"
+  echo ""
+  echo "  git add -u"
+  echo "  git commit"
+  echo ""
+  exit 1
+fi
+
+echo "✅ Code formatting looks good!"
+exit 0

CONTRIBUTING.md

@@ -22,6 +22,24 @@ For a big feature it's advised to raise an issue to discuss it first.
 * To quickly get up and running, you can just run `dotnet build SentryNoMobile.slnf` (you're skipping the mobile targets)
 * To run a full build in Release mode and test, before pushing, run `./build.sh` or `./build.cmd`
 
+## Git Hooks (Optional but Recommended)
+
+To automatically verify code formatting before committing, you can set up a pre-commit hook:
+
+```bash
+./scripts/setup-hooks.sh
+```
+
+This configures git to run `dotnet format --verify-no-changes` before each commit. If formatting issues are found, the commit will be prevented and you'll need to run:
+
+```bash
+dotnet format Sentry.slnx --no-restore --exclude ./modules ./**/*OptionsSetup.cs ./test/Sentry.Tests/AttributeReaderTests.cs
+```
+
+Then stage the formatting changes and commit again. This helps catch formatting issues early and reduces CI failures.
+
+**Note:** You can bypass the hook for a specific commit using `git commit --no-verify` if needed.
+
 ## Minimal Dependencies
 
 * The latest versions of the following .NET SDKs:

scripts/setup-hooks.sh

@@ -0,0 +1,14 @@
+#!/bin/bash
+set -e
+
+echo "Setting up git hooks..."
+
+# Configure git to use .githooks directory for hooks
+git config core.hooksPath .githooks
+
+echo ""
+echo "✅ Git hooks configured successfully!"
+echo ""
+echo "The pre-commit hook will now verify code formatting before each commit."
+echo "To bypass the hook for a specific commit, use: git commit --no-verify"
+echo ""