docs: document branch protection rules in README and CONTRIBUTING (#61)

Add branch protection information to help contributors understand the new workflow:
- README.md: Update Publishing section to clarify PR-required flow
- CONTRIBUTING.md: Add Branch Protection section with rule details
The main branch now requires PRs, CI checks, signed commits, and linear history.

🖥️ IDE: [Cursor](https://cursor.sh)
🔌 Extension: [Claude Code](https://claude.ai/download)


Model-Raw: claude-opus-4-5-20251101

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

Author: nullvariant

CONTRIBUTING.md

@@ -2,6 +2,17 @@
 
 Thank you for your interest in contributing to nullvariant-vscode-extensions!
 
+## Branch Protection
+
+The `main` branch is protected with the following rules:
+
+- **Pull Request required**: All changes must go through a PR (direct push is disabled)
+- **CI status checks**: The `build` check must pass before merging
+- **Signed commits required on main**: Commits merged to `main` must be GPG signed (handled by maintainers during merge)
+- **Linear history**: Rebase/squash merging is required (no merge commits)
+
+> **Note for contributors**: You don't need to GPG-sign your commits. The maintainer will handle signing when merging your PR.
+
 ## Getting Started
 
 1. Fork the repository
@@ -11,6 +22,7 @@ Thank you for your interest in contributing to nullvariant-vscode-extensions!
 5. Commit with a descriptive message
 6. Push to your fork
 7. Open a Pull Request
+8. Wait for CI checks to pass, then a maintainer will merge
 
 ## Development Setup
 
@@ -19,6 +31,9 @@ Thank you for your interest in contributing to nullvariant-vscode-extensions!
 git clone https://github.com/your-username/nullvariant-vscode-extensions.git
 cd nullvariant-vscode-extensions
 
+# Set up git hooks (recommended)
+git config core.hooksPath .githooks
+
 # Install dependencies
 npm install
 

README.md

@@ -87,15 +87,24 @@ nullvariant-vscode-extensions/
 └── README.md
 ```
 
-## Publishing
+## Publishing (Maintainers Only)
 
-Extensions are automatically published when a tag is pushed:
+> **Note**: The `main` branch is protected. All changes must go through a Pull Request.
+
+Extensions are automatically published when a release tag is pushed:
+
+1. Ensure all changes are merged to `main` via Pull Request
+2. Create and push a release tag from the latest `main`:
 
 ```bash
-git tag git-id-switcher-v0.1.0
-git push origin git-id-switcher-v0.1.0
+git checkout main
+git pull origin main
+git tag git-id-switcher-v1.0.0
+git push origin git-id-switcher-v1.0.0
 ```
 
+The [publish workflow](.github/workflows/publish.yml) will automatically build and publish the extension to VS Code Marketplace and Open VSX.
+
 ## License
 
 MIT