✅ By default, only YOU can modify the main branch ✅ Others can only suggest changes via Pull Requests ✅ You must approve every change before it goes live

• Owner: You (full control)
• Collaborators: Anyone you specifically invite (limited permissions)
• Everyone else: Can fork, report issues, suggest changes via PR

1. Go to: https://github.com/vineet454/PromptZip
2. Click Settings (top right)
3. Click Branches (left sidebar)
4. Click Add rule under "Branch protection rules"
5. Enter main as the branch name
6. Check these options:

✅ Require pull request reviews before merging
   ├─ Required number of approvals: 1
   └─ Require review from code owners

✅ Require status checks to pass before merging
   ├─ GitHub Actions (tests must pass)

✅ Require branches to be up to date before merging

✅ Dismiss stale pull request approvals when new commits are pushed

✅ Restrict who can push to matching branches
   └─ Only allow specified people to push

7. Click Create

1. Create a file named CODEOWNERS in the root:

# CODEOWNERS
# @vineet454 is the owner of everything
*       @vineet454

2. Commit and push:

git add CODEOWNERS
git commit -m "Add CODEOWNERS file"
git push

3. Now you'll automatically be requested for review on all PRs

1. Go to Settings
2. Scroll to Features
3. Uncheck Discussions (if you don't want them)

If someone submits a PR you don't want:

1. Open the Pull Request
2. Scroll to bottom
3. Click Close pull request
4. Add a comment explaining why (e.g., "This repository is not accepting contributions at this time")
5. The PR closes without merging

✅ Repository: https://github.com/vineet454/PromptZip ✅ Visibility: Public (anyone can see it) ✅ Write Access: Only you ✅ Push Protection: Default GitHub protection active ✅ Pull Requests: You control all merges

Owner: @vineet454 ✅
Collaborators: None (unless you invite)
Branch Protection: Recommended (instructions above)
Pull Request Reviews: Recommended (you are sole reviewer)
CI/CD Tests: Already configured ✅ (runs on all PRs)

• ✅ Free
• ✅ Anyone can see your code
• ✅ Anyone can fork it
• ✅ You control all direct changes
• ✅ Good for community contributions

• Only people you invite can see it
• GitHub Personal plans offer private repos
• More restrictive, less open source

• Branch protection: No
• Reviews required: No
• Anyone can submit PRs
• Risk: Low (you control merges)
• Recommendation: Good for open source

• Branch protection: Yes
• Reviews required: Yes (from you)
• Tests must pass
• Stale reviews dismissed
• Risk: Very Low
• Recommendation: Best for most projects

• All from Option 2, plus:
• Only you can push (even after PR approval)
• Require admin approval for merges
• Require all conversations resolved
• Risk: None
• Recommendation: For critical projects only

Your code is protected by default!

• ❌ No one can directly edit your main branch
• ✅ All changes go through Pull Requests
• ✅ You approve or reject every change
• ✅ GitHub tracks who changed what
• ✅ You can revert any merge instantly

If you don't want ANY contributions:

1. Go to Settings
2. Click Features
3. Uncheck Sponsorships and Discussions
4. Edit CONTRIBUTING.md to say "This project is not accepting contributions"
5. People can still fork it, but won't be encouraged to contribute

# See the commit you want to undo
git log --oneline

# Revert the commit
git revert <commit-hash>

# Push the revert
git push

The bad change will be undone instantly!

Your GitHub Repository Security Status:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✅ Only you can push to main
✅ All PRs require your approval
✅ CI/CD tests run automatically
✅ Changes are tracked
✅ You can revert anything
✅ Your code is safe!
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Recommendation: Follow Option 2 (Medium Security) for the best balance between security and open-source collaboration.

Need help with setup? Check the instructions above!