Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/paritytech/substrate-tip-bot

A GitHub bot to submit tips on behalf of contributors
https://github.com/paritytech/substrate-tip-bot

Last synced: 3 months ago
JSON representation

A GitHub bot to submit tips on behalf of contributors

Awesome Lists containing this project

README 

        
# substrate-tip-bot



[![GitHub Issue Sync](https://github.com/paritytech/substrate-tip-bot/actions/workflows/github-issue-sync.yml/badge.svg)](https://github.com/paritytech/substrate-tip-bot/actions/workflows/github-issue-sync.yml)



> A GitHub App built with [Probot](https://github.com/probot/probot) that can submit tips on behalf

> of a [Substrate](https://github.com/paritytech/substrate) based network.



# Getting started 🌱



## Usage



This bot relies on GitHub pull request that opt in via a body text comment (or text in profile bio) to specify what Substrate network and address to send tips to.  



Permission to send out tips is limited for a GitHub team, that's configured with `APPROVERS_GH_ORG` + `APPROVERS_GH_TEAM` environment variables. For production, it's [@paritytech/tip-bot-approvers](https://github.com/orgs/paritytech/teams/tip-bot-approvers)  



### Pull request body



```sh

{kusama|polkadot|rococo|westend} address: 

```



Followed by a _comment_ on said pull request



### Pull request comment



```sh

/tip {small | medium | large | }

```



In OpenGov, the tip sizes are translated to specific values as follows:



Size | Value on Kusama | Value on Polkadot

--- | --- | ---

small | 4 KSM | 20 DOT

medium | 16 KSM | 80 DOT

large | 30 KSM | 150 DOT



## Local development 🔧



To use this bot, you'll need to have an `.env` file. Most of the options will

automatically be generated by the GitHub application creation process, but you will also need to add

`ACCOUNT_SEED`, `APPROVERS_GH_ORG` and `APPROVERS_GH_TEAM`.



A reference env file is placed at `.env.example` to copy over



```sh

$ cp .env.example .env

```



### Run network locally



- Follow readme in https://github.com/paritytech/polkadot#development to run local network. 

  - Among all dependencies, main steps are (from repo): 

    - Compile `cargo b -r`

    - Run `./target/release/polkadot --dev`

  - Alternatively, run a docker container: `docker run -p 9933:9933 -p 9944:9944 parity/polkadot --dev`

- [Create 2 accounts: for "bot" & for "contributor"](https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/accounts) 

  - Save the seeds & passwords somewhere

  - Set `ACCOUNT_SEED` as bot's seed in `.env` file  

- Create a team in GitHub for the org that you control, and set `APPROVERS_GH_ORG` and `APPROVERS_GH_TEAM` in `.env` to said org and team

- Set `LOCALNETWORKS=true` in `.env`, to change the endpoints

- Transfer some meaningful amount from test accounts (like Alice) to a new bot account (from which bot will send tip to the contributor)



### Create GitHub application for testing



- Note: During app creation save according env variables to `.env` file

- Read [Getting-started](https://gitlab.parity.io/groups/parity/opstooling/-/wikis/Bots/Development/Getting-started) doc to get a sense of how to work with bots

- Follow [creating app](https://gitlab.parity.io/groups/parity/opstooling/-/wikis/Bots/Development/Create-a-new-GitHub-App)

and [installing app](https://gitlab.parity.io/groups/parity/opstooling/-/wikis/Bots/Development/Installing-the-GitHub-App)

guidance

- `WEBHOOK_PROXY_URL` you can generate via https://smee.io/new



### Integration tests



There are integration tests that execute the tip functions against a locally running Polkadot and Kusama nodes.



The tests will spin up the local nodes automatically.



To run the tests:



Build the application image:

```bash

yarn build:docker

```



Then run the tests:



```bash

yarn test:integration

```



#### Github app permissions



##### Repository permissions:

- **Issues**: Read-only

  - Allows for interacting with the comments API

- **Pull Requests**: Read & write

  - Allows for posting comments on pull requests

##### Organization permissions

- **Members**: Read-only

  - Related to $ALLOWED_ORGANIZATIONS: this permission enables the bot to request the organization membership of the command's requester even if their membership is private

##### Event subscriptions

- **Issue comment**

  - Allows for receiving events for pull request comments



### Start a bot



After registering and configuring the bot environment, we can run it.



```sh

$ yarn start

```



### Create a PR and test it

You'll need 2 gh users: contributor and maintainer (since it's not allowed for contributors to send a tip to themselves)



- From contributor GH account: create a PR and add into PR description `rococo address: `

- From maintainer GH account: write `/tip small` in comments so the bot sends funds to 



### Docker



To run the bot via Docker, we need to build and then run it like so



```sh

$ docker build -t substrate-tip-bot .

```



```sh

$ docker run \

    -e APP_ID= \

    -e PRIVATE_KEY= \

    substrate-tip-bot

```



## End-to-end tests



For the E2E tests, we need a modified Rococo node in a way that speeds up the referenda and treasury.



### Preparing and running Rococo



```bash

git clone https://github.com/paritytech/polkadot-sdk.git

cd polkadot-sdk

git checkout polkadot-v1.15.0

git apply ../polkadot.e2e.patch

cargo build --release --locked --features=fast-runtime -p polkadot

./target/release/polkadot --rpc-external --no-prometheus --no-telemetry --chain=rococo-dev --tmp --alice --execution Native --unsafe-force-node-key-generation --rpc-port 9902

```



You might need to fund the treasury (`13UVJyLnbVp9RBZYFwFGyDvVd1y27Tt8tkntv6Q7JVPhFsTB`) if it is broke.



#### Patch



The `polkadot-sdk` code is patched (see the line doing `git apply`) - that's why we have to build the code from source, instead of using a released binary or docker image.



The patch involves changing the timelines around OpenGov mechanics, so that we can test the whole flow in a reasonable amount of time.



### Running the E2E tests



```bash

yarn test:e2e

```



Go make a cup of tea, the tests take ~3 minutes (waiting for the various on-chain stages to pass).



On CI, the E2E tests are running:



- On every PR and commits pushed to `master`, against a fixed release of `polkadot-sdk`.

- Periodically, against a most recent release of `polkadot-sdk`.



The tests are running in a container specified by `E2E_TESTS_CONTAINER` [repository variable](https://docs.github.com/en/actions/learn-github-actions/variables#defining-configuration-variables-for-multiple-workflows).



The container version should be kept in sync with the container used in [`polkadot-sdk` CI](https://github.com/paritytech/polkadot-sdk/blob/polkadot-v1.7.2/.github/workflows/fmt-check.yml#L18).



## Contributing



If you have suggestions for how substrate-tip-bot could be improved, or want to report a bug, open

an issue! We'd love all and any contributions.



For more, check out the [Contributing Guide](CONTRIBUTING.md).



## License



[MIT](LICENSE) © 2021 Parity Technologies