From a40e2eaef3f7bbe0addd45e9f43eec46f22a0ce6 Mon Sep 17 00:00:00 2001 From: MeirGavish Date: Wed, 12 Aug 2026 16:59:48 +0300 Subject: [PATCH] Add guidelines to refer to issues to CONTRIBUTING.md (#610) * Add guidelines to check and open issues to CONTRIBUTING.md * A few rephrases Co-authored-by: MeirGavish * Another small rephrase --- CONTRIBUTING.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 39fadbed..2f05bed4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,6 +2,15 @@ Thank you for reading this. Below is a quick summary of expectations and tips to contribute. +## Making Contributions +First check the repo's [open issues](https://github.com/GBALATRO/balatro-gba/issues) to see if there is anything you want to take, the ["good first issue" label](https://github.com/GBALATRO/balatro-gba/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22) can be a good place to start but feel free to check others too. + +If an issue is assigned to someone it usually means it's already being worked on and it's probably best to avoid working on it but feel free to join the issue discussion if there's anything you have to add. + +If you see an unassigned issue you want to work on, add a comment there saying you want to work on it and we will assign it to you. It is recommended to discuss the planned implementation before opening a PR so it is approved before you fully commit to working on it. + +If there's something you want to add or fix and there's no open issue for it, open a new one, and as before, convey your intention to work on it and discuss the planned implementation. + ## Scope We are limiting the scope of the project in order to not compete with the original Balatro and avoid a takedown by Playstack. We limited the scope to 52 jokers and reached that limit so currently there is no plan to add more jokers.