diff --git a/repository_structure.html b/repository_structure.html
index 45aa390066..6ac7d71f2b 100644
--- a/repository_structure.html
+++ b/repository_structure.html
@@ -332,6 +332,8 @@ <h2><a class="anchor" id="git-usage"></a>
 </div><!-- fragment --><ul>
 <li>After committing changes, create a pull request (using the github web UI)</li>
 <li>Follow these <a class="el" href="contribute.html#git-commits-and-pull-requests">guidelines</a> to write commit messages and open pull requests.</li>
+<li>For every pull request opened, a standard set of CI tests will run automatically. If any of these fail, look at the Github page for your pull request for the list of tests that have been run. There should be "Details" links there for any tests that have failed. Ask for help via messages in comments on your PR if you are not able to determine the cause of the failures.</li>
+<li>There are several CI tests that are not run on every pull request automatically, but only via following the steps below, in order to reduce the compute resources used on every pull request. If you wish to run one or more of these, look through the list of Github labels for the p4c project <a href="https://github.com/p4lang/p4c/labels">here</a> for labels whose name begins with "runs-". Add one or more of those labels to your PR. On all future pushes to the branch of that PR, those additional CI runs should run.</li>
 </ul>
 <h2><a class="anchor" id="debugging"></a>
 Debugging</h2>