Group Review Bot
================

This workaround is mainly needed because Gitea does not track which team member performed a review on behalf of a team.

Main Tasks
----------

Awaits a comment in the format “@groupreviewbot-name: approve”, then approves the PR with the comment “<user> approved a review on behalf of <groupreviewbot-name>.”

Target Usage
------------

Projects where policy reviews are required.

Configuration
--------------

The bot is configured via the `ReviewGroups` field in the `workflow.config` file, located in the ProjectGit repository.

See `ReviewGroups` in the [workflow-pr configuration](../workflow-pr/README.md#config-file).

```json
{
  ...
  "ReviewGroups": [
    {
      "Name": "name of the group user",
      "Reviewers": ["members", "of", "group"],
      "Silent": "(true, false) -- if true, do not explicitly require review requests of group members"
    }
  ],
  ...
}
```

Server configuration
--------------------------

**Configuration file:**

| Field | Type | Notes |
| ----- | ----- | ----- |
| root | Array of string  | Format **org/repo\#branch** |

Requirements
------------
Gitea token with following permissions:
- R/W PullRequest
- R/W Notification
- R User

Env Variables
-------------
The following variables can be used (and override) command line parameters.

  * `AUTOGITS_CONFIG` - config file location
  * `AUTOGITS_URL` - Gitea URL
  * `AUTOGITS_RABBITURL` - RabbitMQ url
  * `AUTOGITS_DEBUG` - when set, debug level logging enabled

Authentication env variables
  * `GITEA_TOKEN` - Gitea user token
  * `AMQP_USERNAME`, `AMQP_PASSWORD` - username and password for rabbitmq