Skip to content

Commit 37a6471

Browse files
committed
deploy: c6518a0
1 parent ca3d594 commit 37a6471

File tree

5 files changed

+19
-5
lines changed

5 files changed

+19
-5
lines changed

.doctrees/CONTRIBUTING.doctree

2.41 KB
Binary file not shown.

.doctrees/environment.pickle

0 Bytes
Binary file not shown.

CONTRIBUTING.html

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -512,8 +512,14 @@ <h2>Two approaches to contributing<a class="headerlink" href="#two-approaches-to
512512
</section>
513513
<section id="forking-the-repository">
514514
<h2>Forking the repository<a class="headerlink" href="#forking-the-repository" title="Link to this heading">#</a></h2>
515-
<p>Independently of the approach you choose, the first step is to fork the Python Packaging Guide repository into your personal GitHub space.</p>
516-
<p><em><strong>TODO</strong>: This section should show a beginner user how to fork a repository in GitHub.</em></p>
515+
<p>Independently of the approach you choose, the first step is to fork the Python Packaging Guide repository into your personal GitHub space. To “fork” a repository in GitHub means to create a copy of the main repository, or repo, that you have complete control over and can modify as you see fit.</p>
516+
<p>To fork a repo,</p>
517+
<ol class="arabic simple">
518+
<li><p>Make sure you are logged into GitHub.</p></li>
519+
<li><p>Go to the repo you would like to fork, in this case the <a class="reference external" href="https://www.github.com/pyopensci/python-package-guide">Python Packaging Guide</a> repo.</p></li>
520+
<li><p>In the top right-hand corner of the page there is a ‘Fork’ button. Click that button. You will be brought to a new page where you will ‘Create a new fork’. Feel free to keep all the default inputs and click ‘Create fork’. This will create a copy of the repo at <code class="docutils literal notranslate"><span class="pre">https://github.com/&lt;username&gt;/python-package-guide</span></code>, where <code class="docutils literal notranslate"><span class="pre">&lt;username&gt;</span></code> is your GitHub username.</p></li>
521+
</ol>
522+
<img width="395" alt="fork_repo" src="https://github.com/user-attachments/assets/949223fb-b58b-4b6d-85db-003bd117da46">
517523
</section>
518524
<section id="contributing-via-the-github-website">
519525
<h2>Contributing via the GitHub website<a class="headerlink" href="#contributing-via-the-github-website" title="Link to this heading">#</a></h2>

_sources/CONTRIBUTING.md.txt

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,17 @@ The second approach is making your contribution directly in the GitHub website.
3232

3333
## Forking the repository
3434

35-
Independently of the approach you choose, the first step is to fork the Python Packaging Guide repository into your personal GitHub space.
35+
Independently of the approach you choose, the first step is to fork the Python Packaging Guide repository into your personal GitHub space. To "fork" a repository in GitHub means to create a copy of the main repository, or repo, that you have complete control over and can modify as you see fit.
3636

37-
*__TODO__: This section should show a beginner user how to fork a repository in GitHub.*
37+
To fork a repo,
38+
39+
1. Make sure you are logged into GitHub.
40+
41+
2. Go to the repo you would like to fork, in this case the [Python Packaging Guide](https://www.github.com/pyopensci/python-package-guide) repo.
42+
43+
3. In the top right-hand corner of the page there is a 'Fork' button. Click that button. You will be brought to a new page where you will 'Create a new fork'. Feel free to keep all the default inputs and click 'Create fork'. This will create a copy of the repo at `https://github.com/<username>/python-package-guide`, where `<username>` is your GitHub username.
44+
45+
<img width="395" alt="fork_repo" src="https://github.com/user-attachments/assets/949223fb-b58b-4b6d-85db-003bd117da46">
3846

3947
## Contributing via the GitHub website
4048

searchindex.js

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)