-
Notifications
You must be signed in to change notification settings - Fork 500
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
Set up vacation bot & enable it for the next two weeks #3999
Conversation
PTAL @seanlip |
Define codeowners for .devbots directory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine, thanks -- I'm not sure whether you need the issue comment message, tbh (normally other folks triage issues, right?), but up to you.
.devbots/vacation.yml
Outdated
issue-comment: > | ||
Thanks for filing this issue! Please note that some team members | ||
are currently taking time off to recharge, so it might be a | ||
while before we respond or triage this issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
respond --> respond to
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch--done.
Hi @BenHenning, this PR is ready to be merged. Please address any remaining comments prior to merging, and feel free to merge this PR once the CI checks pass and you're happy with it. Thanks! |
Address reviewer comment.
Thanks @seanlip!
Not always. Since we don't have an established triage process yet, this is partly a stop-gap since I've been making a hint to follow up with issues when necessary over the last few weeks. |
OK! Sg, your call. |
Explanation
This PR sets up a vacation bot so that at times when we don't have hand-over plans for core team members, we can provide a general notice to the community that there may be delays. Since I'm going to be unavailable for the next two weeks, I'm enabling this until 6 December (#3998 is tracking disabling it).
Note that the validation that this was set up correctly will be done by verifying the message starts showing up tomorrow (I enabled it a day early for this reason).
Essential Checklist
The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)For UI-specific PRs only
N/A -- this is setting up a bot.