Architecture Discusion #2

Open
opened 2020-02-09 19:13:31 +00:00 by 6543 · 3 comments
Contributor

this issue is about talking how staletea is architectured and how it should work

this issue is about talking how staletea is architectured and how it should work
Author
Contributor
  • activate repo

    • add repoID to repo-table
    • read staletea conf and set params into repo-table
    • query all afected (open) issue and write them to issue-table
  • new commit on default branch: check if staletea conf changed, if ture:

    • update params of repo-table
    • if ignore lable changes etc ...
      -> query all afected (open) issue and write/update them to issue-table
  • on issue change

    • check if issue in db if not(check if afected and insert-into/delete-on issue-table)
    • else check if issue is afected (open&lables) -> insert into db
  • cron

    • query per repo-setting ... issues and poste messages / close them
* activate repo * add repoID to repo-table * read staletea conf and set params into repo-table * query all afected (open) issue and write them to issue-table * new commit on default branch: check if staletea conf changed, if ture: * update params of repo-table * if ignore lable changes etc ... -> query all afected (open) issue and write/update them to issue-table * on issue change * check if issue in db if not(check if afected and insert-into/delete-on issue-table) * else check if issue is afected (open&lables) -> insert into db * cron * query per repo-setting ... issues and poste messages / close them
Owner

Thank you for your ideas. We should this split up into multiple issues.

Thank you for your ideas. We should this split up into multiple issues.
jonasfranz added a new dependency 2020-02-15 12:44:29 +00:00
jonasfranz added a new dependency 2020-02-15 12:49:23 +00:00
Owner

There are also some question marks regarding authentication. See #5.

There are also some question marks regarding authentication. See #5.
jonasfranz added a new dependency 2020-02-15 13:22:23 +00:00
jonasfranz added a new dependency 2020-02-15 13:24:19 +00:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Depends on
#3 Activate repository
jonasfranz/staletea
#6 Issue Checkup
jonasfranz/staletea
#7 Issue Cronjob
jonasfranz/staletea
Reference: jonasfranz/staletea#2
No description provided.