Skip to content

Commit b40be6f

Browse files
fix bullet indentation
1 parent 182c73d commit b40be6f

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

doc/developer.contributing.rst

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,8 @@ version.
3737

3838
1. To get started contributing code in the `Gambit GitHub repo <https://github.com/gambitproject/gambit>`__, do one of the following:
3939

40-
- Core developers: request contributor access from one of the `team <https://www.gambit-project.org/team/>`__
41-
- External contributors: fork the repository on GitHub.
40+
- Core developers: request contributor access from one of the `team <https://www.gambit-project.org/team/>`__
41+
- External contributors: fork the repository on GitHub.
4242

4343
2. Clone the repository to your local machine ::
4444

@@ -82,12 +82,12 @@ version.
8282

8383
8. Open a pull request on GitHub to the master branch of the upstream repository. Ensure your pull request:
8484

85-
- Links to any relevant issues.
86-
- Includes a clear description of the changes made.
87-
- Explains how a reviewer can test the changes.
85+
- Links to any relevant issues.
86+
- Includes a clear description of the changes made.
87+
- Explains how a reviewer can test the changes.
8888

89-
.. note::
90-
It's good practice to open a draft pull request early in the development process to facilitate discussion and feedback, ensure there are no merge conflicts, and allow for continuous integration testing via GitHub Actions.
89+
.. note::
90+
It's good practice to open a draft pull request early in the development process to facilitate discussion and feedback, ensure there are no merge conflicts, and allow for continuous integration testing via GitHub Actions.
9191

9292
9. Core developers will review your changes, provide feedback, and merge them into the master branch if they meet the project's standards.
9393

0 commit comments

Comments
 (0)