If build is failing, we should have a nice way of explaining why. There is a random factor in here which says if and how PR will be trolled. Before PR is submitted author doesn't know if and how it will be trolled. That's why, we should provide nice information why build failed ( got trolled ) and what are the steps to make it nice.

As a second step ( if PR was selected for trolling ) there should be a random picker for which troll is assigned to that PR. Those are available trolls: https://github.com/jacekelgda/pr-troll/issues?q=is%3Aissue+is%3Aopen+label%3ATroll

This is the main logic of trolls. Trolls can fail or pass a builds of PR.

There are multiple trolls. Each with different trolling ability. Rules are characteristics of trolls https://github.com/jacekelgda/pr-troll/issues?q=is%3Aissue+is%3Aopen+label%3Arule .

There are two stages of trolling in each created PR.

First level per each PR decides if PR is going to be trolled ( Described in here #11 ). Depending on trolling level there will be a one in a x chance PR is going to be trolled.

Second level applies only for PRs that are trolled. There is a random troll assigned to the PR which should stick with it. Each PR update since assignment should have that troll.

Example:

1. PR was created
2. PR got trolled
3. Random troll assignment - Refactor commit Troll
4. PR build got crashed by the Refactor troll with explanation that refactor commit should be added to that PR.
5. Refactor troll waits for PR update
6. PR was updated
7. Refactor troll found refactor commit in updated PR
8. Troll passes the build for PR and goes away

This troll should check if Readme.md was updated.

One of the first important abilities of troll will be to pinpoint which PR it is from specific author. It could be used for various things. This will lead the way to other functionalities.

This troll should check if some files are stale in the project.

Note: There should be a filter to it to exclude config files and those without living code.

Trolling lvl hard, medium, soft

There should be a place where admin can assign trolling level to a project. Each PR will have a chance of being trolled based on lvl factor.

hard - 80% chance of being trolled
medium - 50% chance of being trolled
soft - 30% chance of being trolled

This is a nice troll. It is a black sheep of the troll family. It will appreciate your consistent contributions. It counts each merged PR by author and give away goods for round numbers.

5, 10, 15, 20 - contributions will be converted to coins!

This troll checks if there was a refactor commit included inside PR. It should be announced what is the commit message format for such commit. This could even be a smart commit addition, example: Normal commit message --refactor #3