mirror of
https://github.com/inspec/inspec
synced 2025-02-25 11:57:17 +00:00
Merge pull request #4430 from inspec/mj/4429
Let expeditor respond to pull requests.
This commit is contained in:
commit
ad47cf0613
2 changed files with 14 additions and 0 deletions
|
@ -146,3 +146,6 @@ subscriptions:
|
||||||
- bash:.expeditor/announce-release.sh:
|
- bash:.expeditor/announce-release.sh:
|
||||||
post_commit: true
|
post_commit: true
|
||||||
- built_in:notify_chefio_slack_channels
|
- built_in:notify_chefio_slack_channels
|
||||||
|
- workload: pull_request_opened:{{agent_id}}:*
|
||||||
|
actions:
|
||||||
|
- post_github_comment:.expeditor/templates/pull_request.mustache
|
||||||
|
|
11
.expeditor/templates/pull_request.mustache
Normal file
11
.expeditor/templates/pull_request.mustache
Normal file
|
@ -0,0 +1,11 @@
|
||||||
|
Hello {{author}}! Thanks for the pull request!
|
||||||
|
|
||||||
|
Here is what will happen next:
|
||||||
|
|
||||||
|
1. Your PR will be reviewed by the maintainers.
|
||||||
|
2. Possible Outcomes
|
||||||
|
a. If everything looks good, one of them will approve it, and your PR will be merged.
|
||||||
|
b. The maintainer may request follow-on work (e.g. code fix, linting, etc). We would encourage you to address this work in 2-3 business days to keep the conversation going and to get your contribution in sooner.
|
||||||
|
c. Cases exist where a PR is neither aligned to Chef InSpec's product roadmap, or something the team can own or maintain long-term. In these cases, the maintainer will provide justification and close out the PR.
|
||||||
|
|
||||||
|
Thank you for contributing!
|
Loading…
Add table
Reference in a new issue