Architecture Discusion #2
Labels
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Depends on
#3 Activate repository
jonasfranz/staletea
#4 Update repository config on change
jonasfranz/staletea
#6 Issue Checkup
jonasfranz/staletea
#7 Issue Cronjob
jonasfranz/staletea
Reference: jonasfranz/staletea#2
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
this issue is about talking how staletea is architectured and how it should work
activate repo
new commit on default branch: check if staletea conf changed, if ture:
-> query all afected (open) issue and write/update them to issue-table
on issue change
cron
Thank you for your ideas. We should this split up into multiple issues.
There are also some question marks regarding authentication. See #5.