Document repo onboarding through secrets

Author: Bastien Abadie

docs/configuration.md

@@ -61,14 +61,6 @@ common:
       # try_name is a display name for that repository
       try_name: try
 
-      # try_mode describes how the try_task_config is published
-      # - json, to build a json v2 try_task_config.json
-      # - syntax, to add a commit with a try syntax as commit message
-      try_mode: json
-
-      # try_syntax is the full commit message used when try_mode = syntax
-      try_syntax: -p xxx -l code-review
-
       # Mercurial checkout mode, several modes available:
       # - robust, to use robustcheckout extension (recommended)
       # - batch, to clone from revision 1 up to tip (slow but lower memory usage)
@@ -79,12 +71,22 @@ common:
       # is setup from a decision task (more details on the bot documentation)
       decision_env_prefix: GECKO
 
+      # Name of the environment variable used by the bot to detect which revision is the head
+      decision_env_revision: GECKO_HEAD_REV
+
+      # Name of the environment variable used by the bot to detect which repository is in use
+      decision_env_repository: GECKO_HEAD_REPOSITORY
+
       # The ssh username (or email) used to push on Try
       ssh_user: someone@mozilla.com
 
       # (Optional) private ssh-key overriding the default one setup in the events main section
       ssh_key: xxxx
 
+      # (Optional) Force the application of the patches on top of the repository tip
+			# instead of the base revision specified by Phabricator
+			use_latest_revision: true
+
 # This main section is only used by the bot project
 bot:
   # The list of reporter classes used to publish issues

docs/new_repository.md

@@ -9,3 +9,35 @@
 ## Contact us
 
 As each new repository has different needs and constraints, please reach out to our team. Look in [README](../README.md) for contact information.
+
+## Onboarding a new repository
+
+⚠️ This section is for code-review bot administrators who wish to add a new repository into the system.
+
+There are 2 places where configuration must be updated: Runtime configuration in Taskcluster, and the backend database.
+
+### Runtime configuration in Taskcluster
+
+You'll need to edit either the [testing](https://firefox-ci-tc.services.mozilla.com/secrets/project%2Frelman%2Fcode-review%2Fruntime-testing) or [production](https://firefox-ci-tc.services.mozilla.com/secrets/project%2Frelman%2Fcode-review%2Fruntime-production) secret that holds the runtime configuration for the bot.
+
+The section to edit in the YAML content is `common.repositories`, which is a list of known repositories.
+
+Each repository has the following structure:
+
+```yaml
+repositories:
+  - checkout: robust
+    try_url: ssh://hg.mozilla.org/try
+    name: mozilla-central
+    ssh_user: reviewbot
+    url: https://hg.mozilla.org/mozilla-unified
+    decision_env_revision: GECKO_HEAD_REV
+    decision_env_repository: GECKO_HEAD_REPOSITORY
+    decision_env_prefix: GECKO
+```
+
+The configuration [is explained in this documentation](./configuration.md) in details.
+
+### Backend database
+
+TODO

docs/projects/bot.md

@@ -198,7 +198,6 @@ common:
   repositories:
     - checkout: robust
       try_url: 'ssh://hg.mozilla.org/try'
-      try_mode: json
       try_name: try
       name: mozilla-central
       ssh_user: <ssh_user>