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

Add comprehensive JSON file monitoring #213

Merged

Conversation

vladh
Copy link
Member

@vladh vladh commented Oct 14, 2024

Closes #113.

When the update-all-members workflow is run, new checks are run for every JSON file:

export enum MemberException {
  JsonFileNotAccessible,
  ReportDueSoon,
  ReportOverdue,
}

If one of these checks is triggered, a GitHub issue is created if it does not already exist:

2024-10-14-15-50-15

2024-10-14-15-50-22

@vladh vladh requested a review from chadwhitacre October 14, 2024 14:55
@vladh vladh force-pushed the vladh/add-better-json-monitoring branch 3 times, most recently from 85b6a75 to 25475b3 Compare October 16, 2024 19:15
@chadwhitacre
Copy link
Contributor

Needs an update to resolve conflicts.

@vladh vladh force-pushed the vladh/add-better-json-monitoring branch from 25475b3 to 51b08cd Compare October 24, 2024 19:36
@vladh
Copy link
Member Author

vladh commented Oct 24, 2024

@chadwhitacre Should be okay now!

@chadwhitacre chadwhitacre merged commit 236d6c0 into opensourcepledge:main Oct 24, 2024
1 check passed
@vladh
Copy link
Member Author

vladh commented Oct 24, 2024

“Should” be! Looks like I missed something in the conflict. Fixing.

@vladh
Copy link
Member Author

vladh commented Oct 24, 2024

Fixed on main.

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

Successfully merging this pull request may close these issues.

Add a slightly more comprehensive way of monitoring JSON files
2 participants