dwyl / dwyl/dwylbot

dwylbot engine

Open
#39 3 comments 3 reactions 2 assignees Claimed by @naazy View on GitHub
enhancement epic help wanted priority-2
Dominant language
Elixir
Stars
28
Forks
7
PR merge metrics
No merged PRs in 30d

Description

link to the two spikes: #6 and especially #21 and #26
This is the main idea how dwylbot will know when to post a comment on Github:
![graph_dwylbot](https://cloud.githubusercontent.com/assets/6057298/25855016/de166604-34c9-11e7-9298-7b803e07bdb2.jpg)

There are still some questions/issues to resolve:
- I assume that the webhooks requests to dwylbot will arrive in order, but this might not be the case so how do we track of the event webhooks?
- If a webhooks which resolves an error arrives and is processed before the previous error has been saved in Postgres (see steps 2 and 3) then dwylbot will only see the error and will post a comment on Github
- I'm not sure that this architecture can scale with a lot of webhooks requests.
- I need to learn how to create parallel timer processes (will need to complete the spike #26 )

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.