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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-137Lines changed: 5 additions & 137 deletions
Original file line number
Diff line number
Diff line change
@@ -15,28 +15,12 @@ Follow either of the two links above to access the appropriate CLA and instructi
15
15
16
16
***NOTE***: Only original source code from you and other people that have signed the CLA can be accepted into the main repository.
17
17
18
-
### Contributing code
19
-
20
-
If you have improvements to TensorFlow, send us your pull requests! For those
21
-
just getting started, Github has a [howto](https://help.github.com/articles/using-pull-requests/).
22
-
23
-
TensorFlow team members will be assigned to review your pull requests. Once the pull requests are approved and pass continuous integration checks, we will merge the pull requests.
24
-
For some pull requests, we will apply the patch for each pull request to our internal version control system first, and export the change out as a new commit later, at which point the original pull request will be closed. The commits in the pull request will be squashed into a single commit with the pull request creator as the author. These pull requests will be labeled as pending merge internally.
25
-
26
-
If you want to contribute but you're not sure where to start, take a look at the
27
-
[issues with the "contributions welcome" label](https://github.com/tensorflow/tensorflow/labels/stat%3Acontributions%20welcome).
28
-
These are issues that we believe are particularly well suited for outside
29
-
contributions, often because we probably won't get to them right now. If you
30
-
decide to start on an issue, leave a comment so that other people know that
31
-
you're working on it. If you want to help out, but not alone, use the issue
make sure your changes are consistent with the guidelines and follow our
23
+
coding style.
40
24
41
25
#### General guidelines and philosophy for contribution
42
26
@@ -45,131 +29,15 @@ TensorFlow coding style.
45
29
changes to lower the maintenance cost.
46
30
* Bug fixes also generally require unit tests, because the presence of bugs
47
31
usually indicates insufficient test coverage.
48
-
* Keep API compatibility in mind when you change code in core TensorFlow,
49
-
e.g., code in [tensorflow/core](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/core) and [tensorflow/python](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/python).
50
-
TensorFlow has reached version 1 and hence cannot make
51
-
non-backward-compatible API changes without a major release. Reviewers of your
52
-
pull request will comment on any API compatibility issues.
53
-
* When you contribute a new feature to TensorFlow, the maintenance burden is (by
54
-
default) transferred to the TensorFlow team. This means that benefit of the
55
-
contribution must be compared against the cost of maintaining the feature.
56
-
* Full new features (e.g., a new op implementing a cutting-edge algorithm)
0 commit comments