Merge remote-tracking branch 'origin/master' into fix-optional-vars-l…

…og-level

.github/CODEOWNERS

@@ -0,0 +1,7 @@
+# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence,
+# @global-owner1 and @global-owner2 will be requested for
+# review when someone opens a pull request.
+*       @tlvu @fmigneault @mishaschwartz

.github/ISSUE_TEMPLATE/bug-report.md

@@ -3,7 +3,7 @@ name: ":bug: Bug Report"
 about: Create an issue related to a bug or encountered problem.
 title: ":bug: [BUG]: "
 labels: bug
-assignees: tlvu, MatProv
+assignees: tlvu, fmigneault, mishaschwartz
 
 ---
 
@@ -45,4 +45,3 @@ Steps to reproduce the behavior:
 
   @tag them below 
 -->
-

.github/ISSUE_TEMPLATE/documentation.md

@@ -3,7 +3,7 @@ name: ":books: Documentation"
 about: Report an issue related to missing, incorrect or insufficient documentation.
 title: ":books: [Documentation]: "
 labels: documentation
-assignees: tlvu
+assignees: tlvu, fmigneault, mishaschwartz
 ---
 
 ## Description

.github/ISSUE_TEMPLATE/feature-request.md

@@ -3,7 +3,7 @@ name: Feature Request
 about: Suggest an idea, new feature or enhancement to existing functionalities.
 title: ":bulb: [Feature]"
 labels: enhancement 
-assignees: tlvu
+assignees: tlvu, fmigneault, mishaschwartz
 
 ---
 
@@ -33,4 +33,3 @@ assignees: tlvu
 
   @tag them below
 -->
-

.github/ISSUE_TEMPLATE/support.md

@@ -3,7 +3,7 @@ name: ":question: Question"
 about: Ask a question or request general help support.
 title: ":question: [Question]: "
 labels: question
-assignees: tlvu, MatProv
+assignees: tlvu, fmigneault, mishaschwartz
 ---
 
 ## Questions

.github/PULL_REQUEST_TEMPLATE.md

@@ -26,9 +26,12 @@ Links to other issues or sources.
 
 - [ ] Things to do...
 
+## CI Operations
+
 <!--
   The test suite can be run using a different DACCS config with ``birdhouse_daccs_configs_branch: branch_name`` in the PR description.
-  To globally skip the test suite regardless of the commit message use ``birdhouse_skip_ci: true`` in the PR description. 
+  To globally skip the test suite regardless of the commit message use ``birdhouse_skip_ci`` set to ``true`` in the PR description.
+  Note that using ``[skip ci]``, ``[ci skip]`` or ``[no ci]`` in the commit message will override ``birdhouse_skip_ci`` from the PR description.
 -->
 
 birdhouse_daccs_configs_branch: master