From 18b8159006c03f2355681ac46c3a8e08b112d3ac Mon Sep 17 00:00:00 2001 From: Ann Almgren Date: Sun, 21 Apr 2019 13:18:53 -0700 Subject: [PATCH] Add more detail about using GitHub issues. --- README.md | 22 +++++++++++++--------- 1 file changed, 13 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 7b23b7eeb4c..5aa417c7680 100644 --- a/README.md +++ b/README.md @@ -34,15 +34,19 @@ Development generally follows the following ideas: If a change is critical, we can cherry-pick the commit from `development` to `master`. - * Contributions are welcomed from anyone. *Any contributions that - have the potential to change answers should be done via pull - requests.* A pull request should be generated from your fork of - amrex and target the `development` branch. - - If there are a number of small commits making up the PR, we may - wish to squash commits upon merge to have a clean history. - *Please ensure that your PR title and first post are descriptive, - since these will be used for a squashed commit message.* + * Bug fixes, questions and contributions of new features are welcome! + + * Bugs should be reported through GitHub issues + * We suggest asking questions through GitHub issues as well + * *Any contributions of new features that have the potential + to change answers should be done via pull requests.* + A pull request should be generated from your fork of + amrex and target the `development` branch. + + If there are a number of small commits making up the PR, we may + wish to squash commits upon merge to have a clean history. + *Please ensure that your PR title and first post are descriptive, + since these will be used for a squashed commit message.* * On the first workday of each month, we perform a merge of `development` into `master`. For this merge to take place, we