Use probot-metadata for storing snooze config #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* require-defaults: Use require to load defaults once
* search-each-repo: Add repo to search query
* require-defaults: Move defaults to js file, get values from env var
* fix-comment-not-found: Use moment to parse time for comment Skip unfreeze if no freeze comment found
* skull-comments: Remove commented out code
|
|
1 task
jbjonesjr
pushed a commit
that referenced
this pull request
Oct 28, 2020
GitHub improvements & Modernization updates
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a spike to use the new probot-metadata to store the snooze config for each issue.
@jbjonesjr I based this off
masteron this fork, which has all of the PRs I've submitted merged together. I tried to cherry pick these changes onto a new branch based off your master, but there were too many conflicts. So I'll wait to submit a PR to this to your upstream repo once the other PRs have been merged.