denoland-deno/.github/ISSUE_TEMPLATE/config.yml

blank_issues_enabled: true
contact_links:
  - name: 🦕 Deploy Feedback
    url: https://github.com/denoland/deploy_feedback/
    about: Provide feature requests or bug reports for the Deno Deploy edge runtime.
  - name: 💬 Discord
    url: https://discord.gg/deno
    about: Join our community on Discord.
chore: issue templates (#20850) Co-authored-by: David Sherret <dsherret@users.noreply.github.com> 2023-11-27 20:14:05 -05:00			`blank_issues_enabled: true`
			`contact_links:`
chore: small changes to issue templates (#21372) 2023-11-28 09:57:21 -05:00			`- name: 🦕 Deploy Feedback`
			`url: https://github.com/denoland/deploy_feedback/`
			`about: Provide feature requests or bug reports for the Deno Deploy edge runtime.`
chore: issue templates (#20850) Co-authored-by: David Sherret <dsherret@users.noreply.github.com> 2023-11-27 20:14:05 -05:00			`- name: 💬 Discord`
chore: fix issue template discord link (#21885) <!-- Before submitting a PR, please read https://deno.com/manual/contributing 1. Give the PR a descriptive title. Examples of good title: - fix(std/http): Fix race condition in server - docs(console): Update docstrings - feat(doc): Handle nested reexports Examples of bad title: - fix #7123 - update docs - fix bugs 2. Ensure there is a related issue and it is referenced in the PR text. 3. Ensure there are tests that cover the changes. 4. Ensure `cargo test` passes. 5. Ensure `./tools/format.js` passes without changing files. 6. Ensure `./tools/lint.js` passes. 7. Open as a draft PR if your work is still in progress. The CI won't run all steps, but you can add '[ci]' to a commit message to force it to. 8. If you would like to run the benchmarks on the CI, add the 'ci-bench' label. --> Fixes https://github.com/denoland/deno/issues/21880 2024-01-10 06:43:45 -05:00			`url: https://discord.gg/deno`
chore: issue templates (#20850) Co-authored-by: David Sherret <dsherret@users.noreply.github.com> 2023-11-27 20:14:05 -05:00			`about: Join our community on Discord.`