The issue/PR should go for the 2.0 release
The issue/PR should go for the 2.1 release
The issue/PR should go for the 2.2 release
The issue/PR should go for the 2.3 release
The issue/PR should go for the 2.4 release
The issue/PR should go for the 2.5 release
The issue/PR should go for the 2.6 release
The issue/PR should go for the 3.0 release
The issue *should* be trivial to solve.
This issue/PR is related to https://hacktoberfest.com
Anyone is free to help, the issue shouldn't be *too* hard.
Priority: critical - must be worked on immediately
Priority: high - should be worked on as soon as reasonable
Priority: low - not important to be worked on
Priority: medium - should be worked on in the near future
Moved from the discord.py github
Status: the issue or PR is awaiting reviews
Status: the issue or PR is in development/progress
This issue/PR is invalid and will not be worked on/merged.
Status: the issue is planned to be worked on
Status: the PR has some pending requested changes
Status: the issue is stalled by other issues
status: the issue requires changes to the documentation or behaviour before it can be completed.
Type: api coverage - this adds code to cover the discord API
Type: bug - something isn't working
Type: docs - improvements or additions to documentation
Type: enhancement - new feature or request
Type: meta - this does not relate to code or documentation
Type: refactor - this is a code change but does not fix a bug/add features
Type: removal - something is removed that may have been deprecated previously