Merge branch 'main' into production

Author: Lulalaby

.github/FUNDING.yml

@@ -0,0 +1,56 @@
+name: Bug Report
+description: Report broken or incorrect behaviour
+labels: unconfirmed bug
+body:
+  - type: markdown
+    attributes:
+      value: >
+        Thanks for taking the time to fill out a bug. If you want real-time support,
+        consider joining our Discord at https://pycord.dev/discord instead.
+
+        Please note that this form is for bugs only!
+  - type: input
+    attributes:
+      label: Summary
+      description: A simple summary of your bug report
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Reproduction Steps
+      description: >
+        What you did to make it happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected Results
+      description: >
+        What did you expect to happen?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Actual Results
+      description: >
+        What actually happened?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: System Information
+      description: Browser / Device information, if applicable.
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: Checklist
+      description: >
+        Let's make sure you've properly done due diligence when reporting this issue!
+      options:
+        - label: I have searched the open issues for duplicates.
+          required: true
+  - type: textarea
+    attributes:
+      label: Additional Context
+      description: If there is anything else to say, please do so here.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Discord Server
+    about: Use our official Discord server to ask for help and questions as well.
+    url: https://pycord.dev/discord

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,38 @@
+name: Feature Request
+description: Suggest a feature for this guide
+labels: feature request
+body:
+  - type: input
+    attributes:
+      label: Summary
+      description: >
+        A short summary of what your feature request is.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: The Problem
+      description: >
+        What problem is your feature trying to solve? What becomes easier or possible
+        when this feature is implemented?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: The Ideal Solution
+      description: >
+        What is your ideal solution to the problem? What would you like this feature to
+        do?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: The Current Solution
+      description: >
+        What is the current solution to the problem, if any?
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Additional Context
+      description: If there is anything else to say, please do so here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+If you find a vulnerability you have two ways to report it:
+
+- Write a dm to one of our core developers on https://pycord.dev/discord
+- Write an email to [email protected]

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,23 +1,23 @@
-# Contributing to Pycord Guide
-
-First of all, thank you for contributing. Contributions help keep the guide up-to-date and make the guide better. Contributions are always welcome.
-
-The following is a set of guidelines for contributing to the guide. These are guidelines, not hard rules.
-
-## Submitting a Pull Request
-
-1. Make sure you are up to date with the latest changes. It is recommended you pull the latest changes from the master branch before working on your own.
-2. Make sure to test your changes before submitting a pull request.
-3. In the guide, make sure to explain everything in a way that is easy to understand. If it's an advanced guide that required some expertise, explain that in a note admonition.
-4. Make sure you follow proper grammar and spelling.
-5. Try to follow the guide's style.
-6. Try to follow git conventions. If you are not familiar with git, you can find a good tutorial [here](https://www.conventionalcommits.org/en/v1.0.0/).
-
-### Licensing
-
-By submitting a pull request, you agree:
-
-1. That you are submitting your own work. You hold the copyright to your work.
-2. To transfer your copyright to the guide.
-3. To license your contribution under the MIT License.
-4. If you are found to be in fault with any of the above, we shall not be held responsible in any way after the pull request has been merged.
+# Contributing to Pycord Guide
+
+First of all, thank you for contributing. Contributions help keep the guide up-to-date and make the guide better. Contributions are always welcome.
+
+The following is a set of guidelines for contributing to the guide. These are guidelines, not hard rules.
+
+## Submitting a Pull Request
+
+1. Make sure you are up to date with the latest changes. It is recommended you pull the latest changes from the master branch before working on your own.
+2. Make sure to test your changes before submitting a pull request.
+3. In the guide, make sure to explain everything in a way that is easy to understand. If it's an advanced guide that required some expertise, explain that in a note admonition.
+4. Make sure you follow proper grammar and spelling.
+5. Try to follow the guide's style.
+6. Try to follow git conventions. If you are not familiar with git, you can find a good tutorial [here](https://www.conventionalcommits.org/en/v1.0.0/).
+
+### Licensing
+
+By submitting a pull request, you agree:
+
+1. That you are submitting your own work. You hold the copyright to your work.
+2. To transfer your copyright to the guide.
+3. To license your contribution under the MIT License.
+4. If you are found to be in fault with any of the above, we shall not be held responsible in any way after the pull request has been merged.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -27,7 +27,7 @@ First, you need to ask Discord to send you events. This is done via "Intents". R
 
 Once you understand what intents are, you can enable the events you need, or just use the default ones with `discord.Intents.all()`.
 
-Now that that's done, let's add an event handler for when a user joins the server. We will use the [`on_member_join` event](https://docs.pycord.dev/en/stable/api.html#discord.on_member_join). We will send a private message to the user welcoming them to the server.
+Now that that's done, let's add an event handler for when a user joins the server. We will use the [`on_member_join` event](https://docs.pycord.dev/en/stable/api/events.html#discord.on_member_join). We will send a private message to the user welcoming them to the server.
 
 ```python
 @bot.event
@@ -37,9 +37,9 @@ async def on_member_join(member):
     )
 ```
 
-We use the [`discord.Bot.event` decorator](https://docs.pycord.dev/en/stable/api.html#discord.Bot.event) to add the event handler. 
+We use the [`discord.Bot.event` decorator](https://docs.pycord.dev/en/stable/api/clients.html#discord.Bot.event) to add the event handler. 
 
-The `on_member_join` event is called when a user joins the server. The `member` parameter is the user that joined. Different events have different names and parameters. You can find all of them [here](https://docs.pycord.dev/en/stable/api.html#discord.Intents).
+The `on_member_join` event is called when a user joins the server. The `member` parameter is the user that joined. Different events have different names and parameters. You can find all of them [here](https://docs.pycord.dev/en/stable/api/data_classes.html#discord.Intents).
 
 So, that's how you add event handlers!