* adds link in README to dev env setup
Matthew Davis authored on 2019/05/02 00:13:20... | ... |
@@ -50,7 +50,7 @@ Get Involved |
50 | 50 |
code to Ansible. |
51 | 51 |
* Join a `Working Group |
52 | 52 |
<https://github.com/ansible/community/wiki>`_, an organized community devoted to a specific technology domain or platform. |
53 |
-* Submit proposed a code update through a pull request to the ``devel`` branch. |
|
53 |
+* Submit a proposed code update through a pull request to the ``devel`` branch. |
|
54 | 54 |
* Talk to us before making larger changes |
55 | 55 |
to avoid duplicate efforts. This not only helps everyone |
56 | 56 |
know what is going on, it also helps save time and effort if we decide |
... | ... |
@@ -63,8 +63,8 @@ Branch Info |
63 | 63 |
|
64 | 64 |
* The ``devel`` branch corresponds to the release actively under development. |
65 | 65 |
* The ``stable-2.X`` branches correspond to stable releases. |
66 |
-* For information about the active branches see the |
|
67 |
- `Ansible release and maintenance <https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html>`_ page. |
|
66 |
+* Create a branch based on ``devel`` and set up a `dev environment <https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_general.html#common-environment-setup>`_ if you want to open a PR. |
|
67 |
+* See the `Ansible release and maintenance <https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html>`_ page for information about active branches. |
|
68 | 68 |
|
69 | 69 |
Roadmap |
70 | 70 |
======= |