cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fixed RST hyperlink issues (#31394)

Browse source
This commit is contained in:
Lindsay Hill 2017-10-06 01:30:10 -07:00 committed by scottb
parent 9a1b495894
commit 146f90e16b
5 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/docsite/rst/community/how_can_I_help.rst
View file

@ -43,7 +43,7 @@ If you should discover that the bug you're trying to file already exists in an i
Review and submit pull requests Review and submit pull requests
------------------------------- -------------------------------
As you become more familiar with how Ansible works, you may be able to fix issues or develop new features yourself. If you think you've got a solution to a bug you've found in Ansible, or if you've got a new feature that you've written and would like to share with millions of Ansible users, read all about the `Ansible development process <http://docs.ansible.com/ansible/latest/community/development_process.rst>` to learn how to get your code accepted into Ansible. As you become more familiar with how Ansible works, you may be able to fix issues or develop new features yourself. If you think you've got a solution to a bug you've found in Ansible, or if you've got a new feature that you've written and would like to share with millions of Ansible users, read all about the `Ansible development process <http://docs.ansible.com/ansible/latest/community/development_process.rst>`_ to learn how to get your code accepted into Ansible.
Another good way to help is to review pull requests that other Ansible users have submitted. The Ansible community keeps a full list of `open pull requests by file <https://ansible.sivel.net/byfile.html>`_, so if there's a particular module or plug-in that particularly interests you, you can easily keep track of all the relevant new pull requests and provide testing or feedback. Another good way to help is to review pull requests that other Ansible users have submitted. The Ansible community keeps a full list of `open pull requests by file <https://ansible.sivel.net/byfile.html>`_, so if there's a particular module or plug-in that particularly interests you, you can easily keep track of all the relevant new pull requests and provide testing or feedback.

2
docs/docsite/rst/community/other_tools_and_programs.rst
View file

@ -17,4 +17,4 @@ of some of the most popular of these tools.
- `Awesome Ansible <https://github.com/jdauphant/awesome-ansible>`_ is a collaboratively curated list of awesome Ansible resources. - `Awesome Ansible <https://github.com/jdauphant/awesome-ansible>`_ is a collaboratively curated list of awesome Ansible resources.
- `Ansible Inventory Grapher <http://github.com/willthames/ansible-inventory-grapher>_` can be used to visually display inventory inheritance hierarchies and at what level a variable is defined in inventory. - `Ansible Inventory Grapher <http://github.com/willthames/ansible-inventory-grapher>`_ can be used to visually display inventory inheritance hierarchies and at what level a variable is defined in inventory.

2
docs/docsite/rst/community/reporting_bugs_and_features.rst
View file

@ -32,4 +32,4 @@ Requesting a feature
The best way to get a feature into Ansible is to submit a pull request. The best way to get a feature into Ansible is to submit a pull request.
The next best way of getting a feature into Ansible is to submit a proposal through the `Ansible proposal process <https://github.com/ansible/proposals>` . The next best way of getting a feature into Ansible is to submit a proposal through the `Ansible proposal process <https://github.com/ansible/proposals>`_.

4
docs/docsite/rst/community/triage_process.rst
View file

@ -2,7 +2,7 @@
Triage Process Triage Process
************** **************
The issue and PR triage processes are driven by the `Ansibot <https://github.com/ansible/ansibullbot>`. Whenever an issue or PR is filed, the Ansibot examines the issue to ensure that all relevant data is present, and handles the routing of the issue as it works its way to eventual completion. The issue and PR triage processes are driven by the `Ansibot <https://github.com/ansible/ansibullbot>`_. Whenever an issue or PR is filed, the Ansibot examines the issue to ensure that all relevant data is present, and handles the routing of the issue as it works its way to eventual completion.
For details on how Ansibot manages the triage process, please consult the `Ansibot For details on how Ansibot manages the triage process, please consult the `Ansibot
Issue Guide <https://github.com/ansible/ansibullbot/blob/master/ISSUE_HELP.md>`. Issue Guide <https://github.com/ansible/ansibullbot/blob/master/ISSUE_HELP.md>`_.

4
docs/docsite/rst/vault.rst
View file

@ -377,7 +377,7 @@ hexlify()'ied result of:
- hexlify()'ed string of the salt, followed by a newline ('\n') - hexlify()'ed string of the salt, followed by a newline ('\n')
- hexlify()'ed string of the crypted HMAC, followed by a newline. The HMAC is: - hexlify()'ed string of the crypted HMAC, followed by a newline. The HMAC is:
- a `RFC2104 <https://www.ietf.org/rfc/rfc2104.txt>` style HMAC - a `RFC2104 <https://www.ietf.org/rfc/rfc2104.txt>`_ style HMAC
- inputs are: - inputs are:
@ -402,6 +402,6 @@ hexlify()'ied result of:
- the plaintext - the plaintext
- the original plaintext - the original plaintext
- padding up to the AES256 blocksize. (The data used for padding is based on `RFX5652 <https://tools.ietf.org/html/rfc5652#section-6.3>`) - padding up to the AES256 blocksize. (The data used for padding is based on `RFX5652 <https://tools.ietf.org/html/rfc5652#section-6.3>`_)