chore: release 4.1.0 (#542)

chore: release 4.1.0

Author: i0bs

.github/FUNDING.yml

@@ -1,3 +1,4 @@
 # These are supported funding model platforms
 
 github: [goverfl0w]
+open_collective: discordinteractions

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Discord server
+    url: https://discord.gg/KkgMBVuEkx
+    about: Join our Discord server for support.

.github/ISSUE_TEMPLATE/report-bug.md

@@ -0,0 +1,81 @@
+name: Report Bug
+description: Create an Issue to report a bug with/about the library.
+title: "[BUG] "
+labels: ["bug"]
+assignees:
+  - goverfl0w
+  - DeltaXWizard
+  - EdVraz
+body:
+  - type: markdown
+    id: thanks
+    attributes:
+      value: |
+        Thank you for taking the time to fill out this bug report!
+        We rely on users to tell us things that we might not find on our own,
+        and your help is greatly valued by the team and others contributing.
+  - type: textarea
+    id: process
+    attributes:
+      label: Describe the bug.
+      description: Please give us an in-depth description of the bug you are having.
+      placeholder: When trying to use feature X, I was unable to make task Y work.
+    validations:
+      required: true
+  - type: textarea
+    id: steps
+    attributes:
+      label: List the steps.
+      description: Please give us a step-by-step process of how you were able to produce this.
+      placeholder: |
+        1. Import the module in Python.
+        2. Create a client variable for the library.
+        3. Try creating a slash command.
+        4. See the traceback error given in the terminal or logger file.
+    validations:
+      required: true
+  - type: textarea
+    id: expectation
+    attributes:
+      label: What you expected.
+      description: Please tell us what you expect for this to do when it ran.
+      placeholder: When I create a slash command, the command should be created and functional.
+    validations:
+      required: true
+  - type: textarea
+    id: result
+    attributes:
+      label: What you saw.
+      description: Please tell us what you found when you actually ran this.
+      placeholder: Instead, I received this traceback error given from my Python terminal.
+      value: |
+        Instead, I received this traceback error given from my Python terminal:
+        ```
+        Traceback (most recent call last):
+          File "A:\Amogus\Python\interactions-bot\main.py", line 6
+            raise SussyBaka("your code doesn't work, silly!")
+                  ^
+
+        SussyBaka: your code doesn't work, silly!
+        ```
+    validations:
+      required: true
+  - type: dropdown
+    id: version
+    attributes:
+      label: What version of the library did you use?
+      multiple: false
+      options:
+        - release
+        - stable
+        - unstable
+    validations:
+      required: true
+  - type: checkboxes
+    id: accept
+    attributes:
+      label: Code of Conduct
+      description: By submitting this Issue, you agree to follow our [contribution requirements.](https://github.com/interactions-py/library/blob/unstable/CONTRIBUTING.rst)
+      options:
+        - label: I agree to follow the contribution requirements.
+          required: true

.github/ISSUE_TEMPLATE/report-bug.yml

@@ -3,7 +3,7 @@ name: Request Feature
 about: Create an Issue to suggest or propose implementing something(s).
 title: "[REQUEST] "
 labels: documentation, enhancement
-assignees: goverfl0w
+assignees: goverfl0w, DeltaXWizard, EdVraz
 
 ---
 

.github/ISSUE_TEMPLATE/request-feature.md

@@ -22,4 +22,4 @@ jobs:
         twine upload dist/*
 on:
   release:
-    types: [created]
+    types: [released]

.github/workflows/ci.yml

@@ -5,18 +5,22 @@ repos:
     - id: requirements-txt-fixer
       name: Requirements
       types: [file]
+      exclude_types: ['image']
     - id: debug-statements
       name: Debugging
       language: python
       types: [file, python]
+      exclude_types: ['image']
     - id: trailing-whitespace
       name: Trailing Whitespace
       language: python
       types: [file]
+      exclude_types: ['image']
     - id: end-of-file-fixer
       name: EOF Newlines
       language: python
       types: [file]
+      exclude_types: ['image']
     - id: check-yaml
       name: YAML Structure
       language: python
@@ -25,7 +29,7 @@ repos:
     - id: check-merge-conflict
       name: Merge Conflicts
   - repo: https://github.com/psf/black
-    rev: 21.12b0
+    rev: 22.1.0
     hooks:
     - id: black
       name: Black Formatting
@@ -47,3 +51,9 @@ repos:
         name: isort Formatting
         language: python
         types: [file, python]
+ci:
+  autoupdate_branch: "unstable"
+  autofix_prs: true
+  autoupdate_commit_msg: "ci: weekly check."
+  autoupdate_schedule: weekly
+  autofix_commit_msg: "ci: correct from checks."

.github/workflows/python-publish.yml

@@ -20,9 +20,11 @@ error may be produced:
 .. code-block:: python
 
     import interactions
-    from logging import DEBUG
+    from logging import basicConfig, DEBUG
 
-    bot = interactions.Client(token="...", log_level=DEBUG) # you can also use -1.
+    basicConfig(level=DEBUG)
+
+    bot = interactions.Client(token="...")
 
     bot.start()
 
@@ -32,28 +34,49 @@ the `Code of Conduct`_ from their documentation.
 Where to start
 --------------
 Our contributions start with an **Issue**. The issue should explain what the problem you're having is.
-Issues are our way and methodology of tracking bugs that may be occuring with this library. In order
-to create create in relevance to the issue, you start a **Pull Request**. Linking the issue in this
+Issues are our way and methodology of tracking bugs that may be occuring with this library. Every contributor
+must start with an Issue, as this helps numerous contributors and developers on various teams keep track of
+requests, bugs and miscellaneous details.
+
+Issue specifications
+********************
+Whenever there is an Issue created, they must follow the according criterion:
+
+- An Issue must not be a duplicate of an existing one.
+- A bug Issue must have all fields filled out.
+- A request Issue must have support from a pre-determined amount of users.
+- A miscellanous Issue must:
+    - Target a third-party repository if it is an issue correlated between the two.
+    - Specify external issues that tie into library installation or performance.
+
+Failure to comply to these factors will result in the Issue being closed with a comment and/or label.
+Some Issues may be closed by the discretion of varying development teams for reasons that exclude
+these factors.
+
+Pull Request specifications
+***************************
+In order to create create in relevance to the issue, you start a **Pull Request**. Linking the issue in this
 (known as a PR) allows us to easily identify what bugs have been correlated with the code requesting
 to be changed in the source, and allow other developers to contribute where needed.
 
 When a PR is made, you **must** be targeting the ``unstable`` branch. This is our development branch
 that we use whenever we're working on any bugfixing, breaking changes and/or overall new features. Our
 development workflow for changes is from this branch to ``stable``, and then from there to a release.
 
-Pull Request specifications
-***************************
-A pull request should adhere to these following requirements:
+A pull request must additionally adhere to these following requirements:
 
-- Each git commit made on your forked project should use `conventional commits`_.
-- The pull request should always be up-to-date with ``unstable``.
+- Each git commit made on your fork must use `conventional commits`_.
+- The pull request must be up-to-date with ``unstable`` before requesting a review.
+- A ``pre-commit`` commit must exist and pass *all* checks before requesting a review.
+- A review must be requested from at least one developer. Please target ``@interactions-py/core`` for this.
 
 Recognizing contributors
 ------------------------
 When a PR is successfully merged into one of the development branches, the GitHub user will automatically
-be added to the contributor list of the repository. Additionally, we also provide a role in our support
-server for contributors. (You will be notified if you are eligible for this.) The git commit history on a
-file will also subsequently be updated by GitHub to include your user signature.
+be added to the contributor list of the repository. Additionally, at the discretion of the core development
+team, it is possible to earn a role in our support server for contributors. (You will be notified if you are
+eligible for this.) The git commit history on a file will also subsequently be updated by GitHub to include
+your user signature.
 
 .. _Code of Conduct: https://github.com/discord/discord-api-docs/blob/master/CODE_OF_CONDUCT.md
 .. _conventional commits: https://www.conventionalcommits.org/en/v1.0.0/