Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closing of issues and milestones needs monitoring #16

Open
luceos opened this issue Jun 4, 2016 · 2 comments
Open

Closing of issues and milestones needs monitoring #16

luceos opened this issue Jun 4, 2016 · 2 comments

Comments

@luceos
Copy link
Member

luceos commented Jun 4, 2016

In order to see whether the requirements of a pledge have been fulfilled, we need to monitor the state of the pledges issues. So;

  • get all issues and milestones that are pledged
    • make sure there are no duplicates
    • read whether the issue/milestone is deleted, if so fire all related events
    • read whether the issue/milestone is completed, if so fire all related events
  • allow setting of a webhook per repository package
    • this will be hitting on a controller that can do the above things
  • set up a cron that does the monitoring regularly
@luceos
Copy link
Member Author

luceos commented Jun 4, 2016

It's very difficult to differentiate between issues that have been closed because they are completed and those that are deleted.

@luceos
Copy link
Member Author

luceos commented Jun 4, 2016

In order to keep this maintainable the process will be the following:

  • Monitor when an item (milestone or issue) was closed. This triggers an event.
  • Listen to the above event sending out an e-mail to all admins.
  • The admin will verify the state of the item and allow it to be marked completed or deleted.
  • If the item is not re-opened within a couple of days we'll pay the pledges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant