Describe the main technical steps of dwylbot

[SimonLab]

As a developer I want to have the main steps and main features I need to implement for dwylbot described in a technical documentation (or issues) so that I can have a general idea of the project and have a clear idea of what needs to be researched and implemented.

At the moment I can think about the main steps of the dwylbot flow:

• Authorise the user with GitHub login How to use dwylbot in any dwyl project (including client projects in different Orgs) #30 review Github OAuth flow #31
• Request list of the user's public repositories and apply dwybot status on each repository (active/inactive) Display dwybot status for public repositories and save status in Postgres #38
• Request list of the organisation's repositories where the user is an administrator of the organisation and apply dwylbot status on each repository Activate dwylbot on organisation's repositories #37
• Save user and list of repositories in Postgres Display dwybot status for public repositories and save status in Postgres #38 database postgres initial structure #41
• Activate/deactive dwylbot on a repository (create/delete webhook on GitHub repo) Display dwybot status for public repositories and save status in Postgres #38
• How should dwylbot react to a GitHub webhook notification? This step requires more thought on how to implement it whilst still being able to scale the application dwylbot engine #39

[SimonLab]

@markwilliamfirth if you could review these steps and let me know if they are clear enough or if you see any other steps that I missed 👍

[ghost]

@SimonLab looks great!

[SimonLab]

all the main steps are now implemented directly by using dwylbot as a Github App