From f43846703a3853d644ea32990e894b2c30d86d67 Mon Sep 17 00:00:00 2001 From: James Goldie Date: Tue, 12 Nov 2024 09:32:33 +1100 Subject: [PATCH] Add discussion ref to CONTRIBUTING.md --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5243c3a..509250a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,7 +2,7 @@ You can contribute to Closeread in many ways: -- By opening issues to provide feedback and share ideas. +- By opening issues and starting discussions to provide feedback and share ideas - By submitting Pull Request (PR) to fix opened issues - By submitting Pull Request (PR) to suggest new features (it is considered good practice to open an issue for discussion before working on a pull request for a new feature). @@ -11,7 +11,7 @@ You can contribute to Closeread in many ways: Pull requests are very welcome! Here's how to contribute via PR: 1. Fork the repository, clone it locally, and make your changes in a new branch specific to the PR. -2. Submit the [pull request](https://help.github.com/articles/using-pull-requests) into the `dev` branch. It is ok to submit as "draft" in your are still working on it but would like some feedback from us. It always good to share in the open that you are working on it. +2. Submit the [pull request](https://help.github.com/articles/using-pull-requests) into the `dev` branch. It is ok to submit as "draft" if you are still working on it but would like some feedback from us. It always good to share in the open that you are working on it. 3. The maintainers will provide feedback on the PR and if its within scope and well-implemented, it will get merged into `dev`. 4. Once there is a critical mass of new features and fixes on `dev`, it will be merged into `main` and a new version of Closeread will be released.