vironment details is helpful and appreciated. 

  * **CI tests failed, what does it mean?** Maybe you need to merge with master or rebase with latest changes. Pushing your changes should re-trigger CI tests. If the tests persist, you’ll want to trace through the error messages and resolve the related issues. 

  * **What are the most high risk changes?** Anything that touches build configuration is an risky area. Please avoid changing these unless you’ve had a discussion with the team beforehand. 

  * **Hey, a commit showed up on my branch, what’s up with that?** Sometimes another community member will provide a patch or fix to your pull request or branch. This is often needed for getting CI tests to pass. 

##  On Documentation  ¶

###  Python Docs  ¶

PyTorch documentation is generated from python source using [ Sphinx
](http://www.sphinx-doc.org/en/master/) . Generated HTML is copied to the docs
folder in the master branch of [ pytorch.github.io
](https://github.com/pytorch/pytorch.github.io/tree/master/docs) , and is
served via GitHub pages.

  * Site: [ http://pytorch.org/docs ](http://pytorch.org/docs)

  * GitHub: [ https://github.com/pytorch/pytorch/tree/master/docs ](https://github.com/pytorch/pytorch/tree/master/docs)

  * Served from: [ https://github.com/pytorch/pytorch.github.io/tree/master/doc ](https://github.com/pytorch/pytorch.github.io/tree/master/docs)

###  C++ Docs  ¶

For C++ code we use Doxygen to generate the content files. The C++ docs are
built on a special server and the resulting files are copied to the [
https://github.com/pytorch/cppdocs ](https://github.com/pytorch/cppdocs) repo,
and are served from GitHub pages.

  * Site: [ http://pytorch.org/cppdocs ](http://pytorch.org/cppdocs)

  * GitHub: [ https://github.com/pytorch/pytorch/tree/master/docs/cpp ](https://github.com/pytorch/pytorch/tree/master/docs/cpp)

  * Served from: [ https://github.com/pytorch/cppdocs ](https://github.com/pytorch/cppdocs)

##  Tutorials  ¶

PyTorch tutorials are documents used to help understand using PyTorch to
accomplish specific tasks or to understand more holistic concepts. Tutorials
are built using [ Sphinx-Gallery ](https://sphinx-
gallery.readthedocs.io/en/latest/index.html) from executable python sources
files, or from restructured-text (rst) files.

  * Site: [ http://pytorch.org/tutorials ](http://pytorch.org/tutorials)

  * GitHub: [ http://github.com/pytorch/tutorials ](http://github.com/pytorch/tutorials)

###  Tutorials Build Overview  ¶

For tutorials, [ pull requests ](https://github.com/pytorch/tutorials/pulls)
trigger a rebuild the entire site using CircleCI to test the effects of the
change. This build is sharded into 9 worker builds and takes around 40 minutes
total. At the same time, we do a Netlify build using _make html-noplot_ ,
which builds the site without rendering the notebook output into pages for
quick review.

After a PR is accepted, the site is rebuilt and deployed from CircleCI.

###  Contributing a new Tutorial  ¶

[ PyTorch.org Tutorial Contribution Guide
](https://github.com/pytorch/tutorials/#contributing)

[ Next ![](../_static/images/chevron-right-orange.svg) ](governance.html
"PyTorch Governance") [ ![](../_static/images/chevron-right-orange.svg)
Previous ](../torchvision/utils.html "torchvision.utils")

* * *

© Copyright 2019, Torch Contributors.

Built with [ Sphinx ](http://sphinx-doc.org/) using a [ theme
](https://github.com/rtfd/sphinx_rtd_theme) provided by [ Read the Docs
](https://readthedocs.org) .

  * PyTorch Contribution Guide 
    * The PyTorch Contribution Process 
    * Getting Started 
      * Proposing new features 
      * Reporting Issues 
      * Implementing Features or Fixing Bugs 
      * Adding Tutorials 
      * Improving Documentation & Tutorials 
      * Participating in online discussions 
      * Submitting pull requests to fix open issues 
      * Reviewing open pull requests 
      * Improving code readability 
      * Adding test cases to make