Skip to content

docs: Consolidate PR collaboration guide to Flagsmith/AGENTS.md #7646

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
emyller wants to merge 4 commits into
base: main
Choose a base branch
from
Open

docs: Consolidate PR collaboration guide to Flagsmith/AGENTS.md #7646

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6f44635
Point to Flagsmith/AGENTS.md PR guidelines
emyller May 29, 2026
dd7fb21
Merge remote-tracking branch 'github/main' into docs/point-to-agents-md
emyller May 29, 2026
47870f5
Try and tell Gemini how to review PRs
emyller May 29, 2026
e73d634
Better wording
emyller May 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gemini/styleguide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Follow https://github.com/Flagsmith/AGENTS.md/blob/main/PR_COLLABORATION.md.
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,10 +21,10 @@ If you are prepared to contribute but are uncertain as to how, consider narrowin
## Submit a PR

1. The target branch should always be set to `main`, unless otherwise asked in the respective issue.
1. Feel free to open a draft pull request. If you open a regular PR, a reviewer will be assigned immediately and your PR will be considered ready for review, unless you specify otherwise in a PR comment. You're welcome to use a PR to run checks against unfinished code.
1. Once you have addressed the review feedback, preferably in new commits, reply to review comments, ensure the checks are passing and re-request a review. It is okay to not address the nitpicks and notes.
1. An approved PR is eventually merged into `main`. Documentation changes will get deployed immediately afterwards. Your frontend changes will get deployed to SaaS, and you can expect both backend and frontend changes to be included in the next release.

To learn how we write PR titles and descriptions, structure reviews, and address feedback, see [PR_COLLABORATION.md](https://github.com/Flagsmith/AGENTS.md/blob/main/PR_COLLABORATION.md). It's the guide our team and review agents follow, and we encourage you to follow it as well.

## Setup local development

The development tooling is intended for use with Linux or macOS, and [GNU Make](https://www.gnu.org/software/make/). Consider using Windows Subsystem for Linux (WSL) to develop on Windows.
Expand Down
Loading