Oppiabot is a GitHub app built with probot. It acts as a helper for the Oppia code repository to maintain the development workflow. It is hosted on Heroku.

The bot currently performs the following functions:

1. Checks whether a contributor creating a pull request has signed the CLA. It adds a label Needs CLA accordingly.

2. Checks merge conflict in a pull request and notifies the author of the pull request if there is a merge conflict.

3. Closes stale pull requests.

Please refer to the following instructions to setup Oppiabot for the first time on your machine:

1. Create a new, empty folder called opensource/ within your home folder. Navigate to it (cd opensource), then fork and clone the Oppiabot repo. This will create a new folder named opensource/oppiabot. Navigate to opensource/oppiabot/.

2. Install Node.Js and NPM on your machine using the following commands:

   First check if you already have Node.js and NPM using:

   node -v
   npm -v

   If these commands show some versions, then you can jump to Point No. 3, else proceed in this point:

   Using Ubuntu

   curl -sL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
   sudo apt-get install -y nodejs

   Using Debian, as root

   curl -sL https://deb.nodesource.com/setup_lts.x | bash -
   apt-get install -y nodejs

   Using MacOS

   sudo brew install node

   Using Windows

   Install using following link. (Its always preferred to use LTS Version).

3. Setup probot and other dependencies by running the following command:

  npm install

4. The Oppiabot uses environment variables. These are configured in the server settings. To deploy the bot locally, create a .env file and copy the contents of .env.example to it. You will need to adjust these variables accordingly following the instructions in the subsequent steps. Run following command to copy .env.example to .env

If you're using Windows cmd, go to Oppiabot folder and type:

copy .env.example .env 

If you have Linux terminal type:

  cp .env.example .env

5. Go to smee.io and click Start a new channel. Set WEBHOOK_PROXY_URL in .env to the URL that you are redirected to.

6. Create a new GitHub App with:

   • Webhook URL: Use your WEBHOOK_PROXY_URL from the previous step.
   • Webhook Secret: development
   • Permissions & events The following permissions and events must be subscribed.If, for example, you only enable issue events, you will not be able to listen on pull request webhooks with the bot.

7. Download the private key. It will be a .pem file. Move it to the root directory of the project. As long as it's in the root directory, it will be automatically detected regardless of the filename.

Make sure you remove

PRIVATE_KEY=example_private_key from .env file, Otherwise app will not work locally.

8. Edit .env and set APP_ID to the ID of the app you just created. The App ID can be found in your app settings page here.

You'll need to identify a target repository and install the bot by clicking the Install button on the settings page of your app, e.g https://github.com/apps/your-app-name. In the .env file put your github account name in WHITELISTED_ACCOUNTS and also add your repository (name in small caps) in the constants.js file locally.

You are now ready to run the bot on your local machine. Run npm run dev to start the server. The dev script will start the bot using nodemon, which will watch for any files changes in your local development environment and automatically restart the server.

$ npm start to start the bot without watching files.

Always run $ npm install and restart the server if package.json has changed. To turn on verbose logging, start server by running: $ LOG_LEVEL=trace npm start. Run npm test to run all the tests locally.

If you have any feature requests or bug reports, please log them on our issue tracker.

Please report security issues directly to [email protected].

The Oppiabot code is released under the Apache v2 license.