@@ -15,22 +15,22 @@ all of which should be in this repository.
15
15
16
16
If you want to report a bug or request a new feature, the most direct
17
17
method is to [ create an
18
- issue] ( https://github.com/cisagov/skeleton-ansible-role-with-test-user/issues ) in
19
- this repository. We recommend that you first search through existing
20
- issues (both open and closed) to check if your particular issue has
21
- already been reported. If it has then you might want to add a comment
22
- to the existing issue. If it hasn't then feel free to create a new
23
- one.
18
+ issue] ( https://github.com/cisagov/skeleton-ansible-role-with-test-user/issues )
19
+ in this repository. We recommend that you first search through
20
+ existing issues (both open and closed) to check if your particular
21
+ issue has already been reported. If it has then you might want to add
22
+ a comment to the existing issue. If it hasn't then feel free to
23
+ create a new one.
24
24
25
25
## Pull requests ##
26
26
27
27
If you choose to [ submit a pull
28
- request] ( https://github.com/cisagov/skeleton-ansible-role-with-test-user/pulls ) , you
29
- will notice that our continuous integration (CI) system runs a fairly
30
- extensive set of linters and syntax checkers. Your pull request may
31
- fail these checks, and that's OK. If you want you can stop there and
32
- wait for us to make the necessary corrections to ensure your code
33
- passes the CI checks.
28
+ request] ( https://github.com/cisagov/skeleton-ansible-role-with-test-user/pulls ) ,
29
+ you will notice that our continuous integration (CI) system runs a
30
+ fairly extensive set of linters and syntax checkers. Your pull
31
+ request may fail these checks, and that's OK. If you want you can
32
+ stop there and wait for us to make the necessary corrections to ensure
33
+ your code passes the CI checks.
34
34
35
35
If you want to make the changes yourself, or if you want to become a
36
36
regular contributor, then you will want to set up
0 commit comments