Simon

A first idea on how to combine errors: Instead of reporting the errors directly on Github we need to collect them during a specific short time and combine the errors....

I manage to start a process which will collect the errors for a give org/repo/issue then combine the errors. I also manage to give a name to the process with...

I need to investigate if we can access all the changes and status of a PR, I would say this is something possible but I will have a deeper look

The GITHUB_ACCESS_TOKEN won't be needed anymore. It was use during my spike to send API requests to Github. The users will have to signup with their Github account to dwylbot,...

@markwilliamfirth I need to update the documentation. dwlbot is now using Github App which provide a private key to send http request to Github

"Creating a PR **without** a blank description will "invite" @dwylbot to generate the PR description", should be with? We only want dwylbot to generate a description only if there is...

dwylbot has now a few rules, should we try to get more user feedback? Should we install dwylbot on all the dwyl repositories, what do you think @markwilliamfirth @iteles @nelsonic...

I'm not sure anymore if this rule is needed. Most of the projects don't update the version of the application. Is this something we still need to investigate?

I think it's a good idea, but we might have to find a solution to let dwylbot add a member to the organisation. I don't think at the moment a...

I notice that if you put your PR to "ready for review" then the last test on the CI is triggered to check that the PR can be merged: ...