Bläddra i källkod

Rename issue template yaml to yml (#2233)

The config.yaml doesn't seem to be getting seen. Judging by https://github.com/carbon-language/carbon-lang/tree/trunk/.github/ISSUE_TEMPLATE ("Customize the issue creation experience with a config.yml file.") I think yaml is allowed for a lot of things (including the templates) but not config.yml.

I'm renaming other files for consistency.
Jon Ross-Perkins 3 år sedan
förälder
incheckning
b0060e5cfb

+ 0 - 0
.github/ISSUE_TEMPLATE/01_explorer_bug.yaml → .github/ISSUE_TEMPLATE/01_explorer_bug.yml


+ 0 - 0
.github/ISSUE_TEMPLATE/02_toolchain_bug.yaml → .github/ISSUE_TEMPLATE/02_toolchain_bug.yml


+ 37 - 0
.github/ISSUE_TEMPLATE/03_issue_for_leads.yml

@@ -0,0 +1,37 @@
+# Part of the Carbon Language project, under the Apache License v2.0 with LLVM
+# Exceptions. See /LICENSE for license information.
+# SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
+
+name: Issue for leads
+description: >
+  Ask the leads for feedback on an important issue, such as a language design
+  choice.
+labels: [issue for leads]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        **Attention:** If this is a _question_, please use either [GitHub
+        Discussions](https://github.com/carbon-language/carbon-lang/discussions)
+        or [Discord](https://discord.gg/ZjVdShJDAs).
+  - type: textarea
+    id: summary
+    attributes:
+      label: >
+        Summary of issue:
+      description: >
+        Provide a short, one-paragraph summary of the issue.
+  - type: textarea
+    id: detail
+    attributes:
+      label: >
+        Details:
+      description: >
+        Provide detailed information about the issue. For example, on a language
+        design choice, it can help to provide various options with a summary of
+        trade-offs.
+  - type: textarea
+    id: extras
+    attributes:
+      label: >
+        Any other information that you want to share?

+ 0 - 0
.github/ISSUE_TEMPLATE/config.yaml → .github/ISSUE_TEMPLATE/config.yml