From 6f446351dc3d3189640a89e10c9e0120d4d1d6b0 Mon Sep 17 00:00:00 2001 From: Evandro Myller Date: Fri, 29 May 2026 14:57:07 -0300 Subject: [PATCH 1/3] Point to Flagsmith/AGENTS.md PR guidelines --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 929bf59025b1..55eeb77d3534 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -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. +For 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 you're welcome to follow it too. + ## 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. From 47870f5780b58583203081586144318d520a6322 Mon Sep 17 00:00:00 2001 From: Evandro Myller Date: Fri, 29 May 2026 15:26:19 -0300 Subject: [PATCH 2/3] Try and tell Gemini how to review PRs --- .gemini/styleguide.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 .gemini/styleguide.md diff --git a/.gemini/styleguide.md b/.gemini/styleguide.md new file mode 100644 index 000000000000..5c5bbcfa833b --- /dev/null +++ b/.gemini/styleguide.md @@ -0,0 +1 @@ +Follow https://github.com/Flagsmith/AGENTS.md/blob/main/PR_COLLABORATION.md. From e73d634be2f1e6c614d3a81167b49d231b153f0d Mon Sep 17 00:00:00 2001 From: Evandro Myller <22429+emyller@users.noreply.github.com> Date: Fri, 29 May 2026 15:42:16 -0300 Subject: [PATCH 3/3] Better wording Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 55eeb77d3534..9944b41199c7 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -23,7 +23,7 @@ If you are prepared to contribute but are uncertain as to how, consider narrowin 1. The target branch should always be set to `main`, unless otherwise asked in the respective issue. 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. -For 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 you're welcome to follow it too. +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