Add branch specifics to Contributing guide (#360)

.github/CONTRIBUTING.md

@@ -28,12 +28,12 @@ Please see pre-commit documentation for further explanation: [Pre-commit](https:
 If you feel like getting your hands dirty, feel free to make the change yourself. Here's how:
 
 1. Fork the repo on Github, and then clone it locally.
-2. Create a branch named appropriately for the change you are going to make.
+2. Create a branch named appropriately for the change you are going to make. Ensure this branch starts from an up to date pull of the `devel` branch (the default branch).
 3. Make your code change.
 4. If you are creating a new role, please add a test for it in our [testing playbooks.](https://github.com/redhat-cop/ah_configuration/blob/devel/playbooks/) by adding a new role entry and adding the appropriate yaml file with test data in the ah_configs directory.
 5. Add a changelog fragment in `changelogs/fragments` as per <https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs>
 6. Push your code change up to your forked repo.
-7. Open a Pull Request to merge your changes to this repo. The comment box will be filled in automatically via a template.
+7. Open a Pull Request to merge your changes to this repo (against the `devel` branch). The comment box will be filled in automatically via a template.
 8. All Pull Requests will be subject to Ansible and Yaml Linting checks. Please make sure that your code complies and fix any warnings that arise. These are checks that appear at the bottom of your Pull Request.
 9. All Pull requests are subject to Testing against being used in automation hub. As above there is a check at the bottom of your pull request for this named integration.