You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h1>Contributing to google/google-api-python-client</h1>
19
+
<p></p>
20
+
21
+
<pclass="view"><ahref="https://github.com/google/google/google-api-python-client">View the Project on GitHub <small>google/google/google-api-python-client</small></a></p>
We'd love to accept your code patches! However, before we can take them, we have to jump a couple of legal hurdles.
35
+
</p>
36
+
37
+
<p>
38
+
Please fill out either the individual or corporate Contributor License Agreement.
39
+
</p>
40
+
41
+
<ul>
42
+
<li>
43
+
If you are an individual writing original source code and you're sure you own the intellectual property, then you'll need to sign an <ahref="https://developers.google.com/open-source/cla/individual">individual CLA</a>.
44
+
</li>
45
+
<li>
46
+
If you work for a company that wants to allow you to contribute your work to <code>google/google-api-python-client</code>, then you'll need to sign a <ahref="https://developers.google.com/open-source/cla/corporate">corporate CLA</a>.
47
+
</li>
48
+
</ul>
49
+
50
+
<p>
51
+
Follow either of the two links above to access the appropriate CLA and instructions for how to sign and return it. Once we receive it, we'll add you to the official list of contributors and be able to accept your patches.
52
+
</p>
53
+
54
+
<h3><aname="discuss" class="anchor" href="#discuss"><spanclass="octicon octicon-link"></span></a>Before writing code, file an issue</h3>
55
+
56
+
<p>
57
+
Use the <ahref="https://github.com/google/google/google-api-python-client/issues">issue tracker</a> to start the discussion. It is possible that someone else is already working on your idea, your approach is not quite right, or that the functionality exists already. The ticket you file in the issue tracker will be used to hash that all out.
We will use github's mechanism for forking repositories and making pull requests. Fork the repository, and make your changes in the forked repository.
64
+
</p>
65
+
66
+
<h3><aname="fork" class="anchor" href="#fork"><spanclass="octicon octicon-link"></span></a>Include tests and update the doc</h3>
67
+
68
+
<p>
69
+
Be sure to add the relevant tests before making the pull request. Additionally, use <code>epydoc</code> to update the documentation. This repository includes a script <code>generate_doc.sh</code> that can be used for this process.
70
+
</p>
71
+
72
+
<h3><aname="fork" class="anchor" href="#fork"><spanclass="octicon octicon-link"></span></a>Make the pull request</h3>
73
+
74
+
<p>
75
+
Once you have made all your changes, tests, and updated the documentation, make a pull request to move everything back into the main <code>google/google-api-python-client</code> repository. Be sure to reference the original issue in the pull request. Expect some back-and-forth with regards to style and compliance of these rules.
76
+
</p>
77
+
78
+
79
+
</section>
80
+
<footer>
81
+
<p>This project is maintained by <ahref="https://github.com/google">google</a></p>
82
+
<p><small>Hosted on GitHub Pages — Theme by <ahref="https://github.com/orderedlist">orderedlist</a></small></p>
0 commit comments