Lines Matching refs:your

13 your own code:
28 Include the following information in your post:
33     your own code.
36 -   List your Python and Jinja versions. If possible, check if this
52 Include the following in your patch:
54 -   Use `Black`_ to format your code. This and other tools will run
57 -   Include tests if your patch adds or changes code. Make sure the test
58     fails without your patch.
73 -   Configure git with your `username`_ and `email`_.
77         $ git config --global user.name 'your name'
78         $ git config --global user.email 'your email'
81 -   Fork Jinja to your GitHub account by clicking the `Fork`_ button.
89 -   Add your fork as a remote to push your work to. Replace
90     ``{username}`` with your username. This names the remote "fork", the
123 .. _username: https://help.github.com/en/articles/setting-your-username-in-git
124 .. _email: https://help.github.com/en/articles/setting-your-commit-email-address-in-git
127 .. _Clone: https://help.github.com/en/articles/fork-a-repo#step-2-create-a-local-clone-of-your-fork
140         $ git checkout -b your-branch-name origin/1.1.x
148         $ git checkout -b your-branch-name origin/master
150 -   Using your favorite editor, make your changes,
153     test fails without your patch. Run the tests as described below.
154 -   Push your commits to your fork on GitHub and
160         $ git push --set-upstream fork your-branch-name
162 …tps://dont-be-afraid-to-commit.readthedocs.io/en/latest/git/commandlinegit.html#commit-your-changes
176 sufficient. CI will run the full suite when you submit your pull
198 Open ``htmlcov/index.html`` in your browser to explore the report.
213 Open ``_build/html/index.html`` in your browser to view the docs.