Add additional github templates and update the expeditor config

.expeditor/config.yml

@@ -1,42 +1,44 @@
 # Documentation available at https://expeditor.chef.io/docs/getting-started/
-
+---
 # Slack channel in Chef Software slack to send notifications about build failures, etc
 slack:
   notify_channel: chef-ws-notify
 
+# This publish is triggered by the `built_in:publish_rubygems` artifact_action.
+rubygems:
+  - chef-apply
+
 github:
-  # The file where the MAJOR.MINOR.PATCH version is kept. The version in this file
-  # is bumped automatically via the `built_in:bump_version` merge_action.
-  version_file: "VERSION"
-  # The file where our CHANGELOG is kept. This file is updated automatically with
-  # details from the Pull Request via the `built_in:update_changelog` merge_action.
-  changelog_file: "CHANGELOG.md"
-  # Delete the PR branch after successfully merged into release branch.
+  # This deletes the GitHub PR branch after successfully merged into the release branch
   delete_branch_on_merge: true
+  # allow bumping the minor release via label
+  minor_bump_labels:
+    - "Expeditor: Bump Version Minor"
+  # allow bumping the major release via label
+  major_bump_labels:
+    - "Expeditor: Bump Version Major"
 
-rubygems:
-  - chef-apply
+changelog:
+  rollup_header: Changes not yet released to rubygems.org
 
 # These actions are taken, in order they are specified, anytime a Pull Request is merged.
 merge_actions:
   - built_in:bump_version:
       ignore_labels:
-        - "Version: Skip Bump"
         - "Expeditor: Skip Version Bump"
         - "Expeditor: Skip All"
   - bash:.expeditor/update_version.sh:
       only_if: built_in:bump_version
   - built_in:update_changelog:
       ignore_labels:
-        - "Meta: Exclude From Changelog"
-        - "Expeditor: Exclude From Changelog"
+        - "Expeditor: Skip Changelog"
         - "Expeditor: Skip All"
   - built_in:build_gem:
-      only_if:
-        - built_in:bump_version
+      only_if: built_in:bump_version
 
 promote:
-  action:
+  actions:
+    - built_in:rollover_changelog
     - built_in:publish_rubygems
 
 subscriptions:

.github/CODEOWNERS

@@ -0,0 +1,7 @@
+# Order is important. The last matching pattern has the most precedence.
+
+*                          @chef/client-workstation
+.expeditor/**              @chef/jex-team
+README.md                  @chef/docs-team
+RELEASE_NOTES.md           @chef/docs-team
+.github/ISSUE_TEMPLATE/**  @chef/docs-team

.github/ISSUE_TEMPLATE.md → .github/ISSUE_TEMPLATE/BUG_TEMPLATE.md

@@ -1,3 +1,9 @@
+---
+name: � Bug Report
+about: If something isn't working as expected �.
+labels: "Status: Untriaged"
+---
+
 ## Description
 <!--- Briefly describe the issue -->
 

.github/ISSUE_TEMPLATE/DESIGN_PROPOSAL.md

@@ -0,0 +1,40 @@
+---
+name: Design Proposal
+about: I have a significant change I would like to propose and discuss before starting
+labels: "Status: Untriaged"
+---
+
+### When a Change Needs a Design Proposal
+
+A design proposal should be opened any time a change meets one of the following qualifications:
+
+- Significantly changes the user experience of a project in a way that impacts users.
+- Significantly changes the underlying architecture of the project in a way that impacts other developers.
+- Changes the development or testing process of the project such as a change of CI systems or test frameworks.
+
+### Why We Use This Process
+
+- Allows all interested parties (including any community member) to discuss large impact changes to a project.
+- Serves as a durable paper trail for discussions regarding project architecture.
+- Forces design discussions to occur before PRs are created.
+- Reduces PR refactoring and rejected PRs.
+
+---
+
+<!---  Proposal description and rationale.  -->
+
+## Motivation
+
+<!---
+    As a <<user_profile>>,
+    I want to <<functionality>>,
+    so that <<benefit>>.
+ -->
+
+## Specification
+
+<!---  A detailed description of the planned implementation. -->
+
+## Downstream Impact
+
+<!---  Which other tools will be impacted by this work?  -->

.github/ISSUE_TEMPLATE/ENHANCEMENT_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+---
+name: 🚀 Enhancement Request
+about: I have a suggestion (and may want to implement it 🙂)!
+labels: "Status: Untriaged"
+---
+
+### Describe the Enhancement:
+<!---  What you are trying to achieve that you can't? -->
+
+### Describe the Need:
+<!---  What kind of user do you believe would utilize this enhancement, and how many users might want this functionality -->
+
+### Current Alternative
+<!--- Is there a current alternative that you can utilize to workaround the lack of this enhancement -->
+
+### Can We Help You Implement This?:
+<!---  The best way to ensure your enhancement is built is to help implement the enhancement yourself. If you're interested in helping out we'd love to give you a hand to make this possible. Let us know if there's something you need. -->

.github/ISSUE_TEMPLATE/SUPPORT_QUESTION.md

@@ -0,0 +1,12 @@
+---
+name: 🤗 Support Question
+about: If you have a question 💬, please check out our Slack!
+---
+
+We use GitHub issues to track bugs and feature requests. If you need help please post to our Mailing List or join the Chef Community Slack.
+
+ * Chef Community Slack at http://community-slack.chef.io/.
+ * Chef Mailing List https://discourse.chef.io/
+
+
+ Support issues opened here will be closed and redirected to Slack or Discourse.

.github/PULL_REQUEST_TEMPLATE.md

@@ -5,11 +5,12 @@
 ### Issues Resolved
 
 [List any existing issues this PR resolves, or any Discourse or
-StackOverflow discussion that's relevant]
+StackOverflow discussions that are relevant]
 
 ### Check List
 
 - [ ] New functionality includes tests
 - [ ] All tests pass
+- [ ] All commits have been signed-off for the Developer Certificate of Origin. See <https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco>
 - [ ] PR title is a worthy inclusion in the CHANGELOG
-- [ ] You have locally validated the change
+- [ ] You have locally validated the change

.github/lock.yml

@@ -0,0 +1 @@
+daysUntilLock: 60

CHANGELOG.md

@@ -1,10 +1,17 @@
-+<!-- latest_release 0.2.12 -->
+<!-- usage documentation: https://expeditor.chef.io/docs/reference/changelog/ -->
+<!-- latest_release 0.2.12 -->
 ## [0.2.12](https://github.com/chef/chef-apply/tree/0.2.12) (2019-05-16)
 
 #### Merged Pull Requests
 - Adding license acceptance passthrough logic [#81](https://github.com/chef/chef-apply/pull/81) ([tyler-ball](https://github.com/tyler-ball))
 <!-- latest_release -->
 
+<!-- release_rollup -->
+<!-- release_rollup -->
+
+<!-- latest_stable_release -->
+<!-- latest_stable_release -->
+
 ## [0.2.11](https://github.com/chef/chef-apply/tree/0.2.11) (2019-02-20)
 
 #### Merged Pull Requests
@@ -212,4 +219,4 @@
 - [SHACK-304] Expeditor should build chef-apply as a gem [#5](https://github.com/chef/chef-apply/pull/5) ([tyler-ball](https://github.com/tyler-ball))
 - [SHACK-250] Renaming the chef-run gem to chef-apply [#1](https://github.com/chef/chef-apply/pull/1) ([tyler-ball](https://github.com/tyler-ball))
 
-+
++