Pull latest from microsoft/vcpkg

.github/ISSUE_TEMPLATE/00-report-package-build-failure.yml

@@ -0,0 +1,47 @@
+name: Report package build failure
+description: Let us know about build failures in ports.
+title: "[<port name>] build failure"
+labels: ["category:port-bug"]
+body:
+  - type: markdown
+    attributes:
+      value: | 
+        ⚠ Please use the generated issue template instead to report a port build failure. ⚠ <br>
+        See [here](https://github.com/microsoft/vcpkg/issues/30604) how to properly report an issue with the latest vcpkg version:
+        <video width="800" controls="controls" muted="muted" src="https://user-images.githubusercontent.com/41973254/229313721-b82c2d3d-b0f9-4e31-98df-08d75831f695.mp4"></video>
+  - type: input
+    id: os
+    attributes:
+      label: Operating system
+      placeholder: "e.g. Windows/Linux etc..."
+    validations:
+      required: true
+  - type: input
+    id: compiler
+    attributes:
+      label: Compiler
+      placeholder: "GCC, Clang, MSVC, MinGW, ..."
+    validations:
+      required: false
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce the behavior
+      placeholder: "`./vcpkg install xxxx`"
+      render: "Shell"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Failure logs
+      description: The console output and all the logs mentioned in the output.
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add any other context about the problem here, such as what you have already tried to resolve the issue.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/01-request-a-new-port.yml

@@ -0,0 +1,36 @@
+name: Request a new port
+description: Request a new port/library that vcpkg should support.
+title: "[New Port Request] <library name here>"
+labels: ["category:new-port", "info:good-first-issue"]
+
+body:
+  - type: input
+    id: name
+    attributes:
+      label: Library name
+    validations:
+      required: true
+  - type: input
+    id: description
+    attributes:
+      label: Library description
+    validations:
+      required: false
+  - type: input
+    id: url
+    attributes:
+      label: Source repository URL
+    validations:
+      required: true
+  - type: input
+    id: homepage
+    attributes:
+      label: Project homepage (if different from the source repository)
+    validations:
+      required: false
+  - type: textarea
+    id: additional-info
+    attributes:
+      label: Anything else that is useful to know when adding (such as optional features the library may have that should be included)
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/02-request-an-update-to-an-existing-port.yml

@@ -0,0 +1,23 @@
+name: Request an update to an existing port
+description: Let us know about a new version of a library we should pick up.
+title: "[<port name>] update to <version>"
+labels: ['category:port-update']
+body:
+  - type: input
+    id: name
+    attributes:
+      label: Library name
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: New version number
+    validations:
+      required: true
+  - type: textarea
+    id: information
+    attributes:
+      label: Other information that may be useful (release notes, etc...)
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/03-request-a-feature-or-improvement-to-a-port.yml

@@ -0,0 +1,29 @@
+name: Request a feature or improvement to a port
+description: Suggest an improvement to one the the ports/libraries in vcpkg.
+title: "[<portname>] <short description of feature>"
+labels: ["category:port-feature"]
+body:
+  - type: textarea
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      placeholder: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Proposed solution
+      placeholder: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe alternatives you've considered
+      placeholder: A clear and concise description of any alternative solutions or features you've considered if applicable.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Additional context
+      placeholder: Add any other context or screenshots about the feature request here.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/04-request-a-feature-or-improvement.yml

@@ -0,0 +1,29 @@
+name: Request a feature or improvement
+description: Suggest an improvement to vcpkg.
+title: ''
+labels: ["category:vcpkg-feature"]
+body:
+  - type: textarea
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      placeholder: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Proposed solution
+      placeholder: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe alternatives you've considered
+      placeholder: A clear and concise description of any alternative solutions or features you've considered.
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Additional context
+      placeholder: Add any other context or screenshots about the feature request here.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/05-other-type-of-bug-report.md

@@ -0,0 +1,31 @@
+---
+name: Other type of bug report
+about: Let us know about an issues that does not fit into any of the other issues.
+  types
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Environment**
+- OS: [e.g. Windows/Linux etc...]
+- Compiler: revision
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. ./vcpkg install xxxx
+2. See error
+Repro code when
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Failure logs**
+-(please attached failure logs)
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: I have a question
+    url: https://github.com/microsoft/vcpkg/discussions
+    about: Please ask and answer questions here.

.github/pull_request_template.md

@@ -1,15 +1,31 @@
-**Describe the pull request**
+<!-- If your PR fixes issues, please note that here by adding "Fixes #NNNNNN." for each fixed issue on separate lines. -->
 
-- #### What does your PR fix?  
-  Fixes #...
+<!-- If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/. -->
 
-- #### Which triplets are supported/not supported? Have you updated the [CI baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)?  
-  <all / linux, windows, ...>, <Yes/No>
+<!-- If this PR updates an existing port, please uncomment and fill out this checklist:
 
-- #### Does your PR follow the [maintainer guide](https://github.com/microsoft/vcpkg/blob/master/docs/maintainers/maintainer-guide.md)?  
-  `Your answer`
+- [ ] Changes comply with the [maintainer guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
+- [ ] SHA512s are updated for each updated download.
+- [ ] The "supports" clause reflects platforms that may be fixed by this new version.
+- [ ] Any fixed [CI baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt) entries are removed from that file.
+- [ ] Any patches that are no longer applied are deleted from the port's directory.
+- [ ] The version database is fixed by rerunning `./vcpkg x-add-version --all` and committing the result.
+- [ ] Only one version is added to each modified port's versions file.
 
-- #### If you have added/updated a port: Have you run `./vcpkg x-add-version --all` and committed the result?  
-  <Yes / I am still working on this PR>
+END OF PORT UPDATE CHECKLIST (delete this line) -->
 
-**If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/**
+<!-- If this PR adds a new port, please uncomment and fill out this checklist:
+
+- [ ] Changes comply with the [maintainer guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
+- [ ] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
+- [ ] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all `find_package` calls are REQUIRED, are satisfied by `vcpkg.json`'s declared dependencies, or disabled with [CMAKE_DISABLE_FIND_PACKAGE_Xxx](https://cmake.org/cmake/help/latest/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html).
+- [ ] The versioning scheme in `vcpkg.json` matches what upstream says.
+- [ ] The license declaration in `vcpkg.json` matches what upstream says.
+- [ ] The installed as the "copyright" file matches what upstream says.
+- [ ] The source code of the component installed comes from an authoritative source.
+- [ ] The generated "usage text" is accurate. See [adding-usage](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/examples/adding-usage.md) for context.
+- [ ] The version database is fixed by rerunning `./vcpkg x-add-version --all` and committing the result.
+- [ ] Only one version is in the new port's versions file.
+- [ ] Only one version is added to each modified port's versions file.
+
+END OF NEW PORT CHECKLIST (delete this line) -->