Fix Version/s: None
Component/s: Stack Documentation and UX
https://developer.lsst.io/stack/adding-a-new-package.html describes how to add Travis CI checks to a repo. I think it can be improved two ways:
- The activation should be done through the Travis CI UI (which they recommend) instead of the GitHub repo's service's settings (which are deprecated).
- Branch protections should be activated only after a repo has successfully been built with Travis. Although this isn't critical, it streamlines the instructions by eliminating some back-and-forth between pages.
A third point is that these instructions should probably be factored into a new how-to topic so that it can service both those setting up new packages and maintaining existing packages.
- mentioned in