RFC feature request which has been accepted.

Pull request which should be auto-closed due proposed changes duplicating already included changes.

Pull request which should be auto-closed due to not following the Contributor Guidelines.

Pull request which should be auto-closed due to a failure to setup EditorConfig.

Pull request which should be auto-closed due to the absence of changes.

Pull request which should be auto-closed due to a messed-up Git history.

Pull request which should be auto-closed due to not following project conventions.

Pull request which should be auto-closed as considered spam.

Pull request which should be auto-closed as considered stale.

Automated issue.

Automated pull request (e.g., from a bot).

Issue or pull requests related to "low-level" functionality oriented toward library consumers.

Pull requests adding or improving benchmarks for measuring performance.

Issue or pull request related to Basic Linear Algebra Subprograms (BLAS).

Pull request needing an automated file check.

Pull request is currently awaiting automation.

Pull request needing applicable lint errors to be automatically fixed.

Pull request needing the latest project code be merged in.

Pull request needing to be rebased on the latest project code.

Pull request needing the copyright years of its files updated.

Issue or pull request specific to browser environments.

Something isn't working.

Issue involves or relates to C.

Issue or pull request specific to continuous integration environments.

Pull request which should skip CI workflows (usually only temporarily to avoid using resources).

Issue or pull request related to project dependencies.

Low degree of difficulty. Should be straightforward to implement and/or resolve.

May require some initial design or R&D, but should be straightforward to resolve and/or implement.