This document provides details on ACME development conventions and practices.
...
important -- Items colored in red mean they are important, and should not be ignored.
one time -- Items colored in green are commands to be issued once per machine.
repo once -- Items colored in orange are commands to be issued once per local repository.
...
Your PR is not finished until it has been merged to master by the Integrator.
This document can be used to help with pull request related issues.
...
This can either be performed on the branch itself, or in an integration branch. The reviewer will inform the developer where testing should take place.
See /wiki/spaces/SE/pages/7998600 for instructions on running the acme_developer test suite. Some additional information can be found at /wiki/spaces/SE/pages/3244819. Results from nightly test suites run on the "next" and "master" branches can be viewed on the ACME CDash website.
Fixing bugs in a new feature
...
Before communicating with remotes, you might want to add or remove remotes. In order to add and remove remotes the git remote command can be used. The two uses are as follows:
git remote add remote-name protocol:address/to/repo # Creates a remote
git remote remove remote-name # Removes a remote
In order to communicate with remotes, there are three actions. push, pull, and fetch.
...