🦠 fix(docs): CONTRIBUTING.md directs PRs to wrong branch

[UniquePixels]

Summary

CONTRIBUTING.md line 102 says to open pull requests against main, but per the Git Flow model, feature PRs should target develop.

Fix

Change "Open a pull request against main" to "Open a pull request against develop".

[coderabbitai]

Coding Plan

Summary

• Single-line documentation fix changing the PR target branch from main to develop
• Aligns contributor instructions with the project's established Git Flow branching model
• No other documentation updates required as confirmed by codebase exploration

Implementation Steps

Update Pull Request Target Branch Documentation

Correct the branch targeting instruction in the contributing guide to align with the Git Flow model used by the project.

Update Branch Reference in CONTRIBUTING.md

Change the pull request target branch from main to develop in the Pull Requests section.

• Update line 102 in CONTRIBUTING.md to read: 4. Open a pull request against \develop``
• The change affects only the fourth step in the Pull Requests section (lines 97–107)
• No other changes are required as this is the sole branch reference in the file

🤖 Prompt for AI agents

Update the pull request target branch reference in `CONTRIBUTING.md` to align
with the project's Git Flow branching model.

- In `CONTRIBUTING.md`, locate line 102 within the Pull Requests section (lines
97–107)
- Change the fourth step to read: `4. Open a pull request against \`develop\``
(replacing `main` with `develop`)
- No other lines or references need to be changed, as this is the only branch
reference in the file

Research

The repository follows a Git Flow branching strategy where feature development targets the develop branch. The CONTRIBUTING.md file provides contribution guidelines including a Pull Requests section (lines 97–107) that currently incorrectly instructs contributors to target main. The exploration confirmed that line 102 is the only reference to branch targeting in the entire file, and no other instances of main or develop exist elsewhere in the document.

---

🚀 Next Steps

🤖 All AI agent prompts combined

Update the pull request target branch reference in `CONTRIBUTING.md` to align
with the project's Git Flow branching model.

- In `CONTRIBUTING.md`, locate line 102 within the Pull Requests section (lines
97–107)
- Change the fourth step to read: `4. Open a pull request against \`develop\``
(replacing `main` with `develop`)
- No other lines or references need to be changed, as this is the only branch
reference in the file

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- `@coderabbitai` You can skip phase 3. Add a simple unit test case for phase 2.
- `@coderabbitai` For design choice 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!