Labels

• Accepted

  RFC feature request which has been accepted.
• autoclose: Already Resolved

  Pull request which should be auto-closed due proposed changes duplicating already included changes.
• autoclose: Contributor Guidelines

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

  Pull request which should be auto-closed due to a failure to setup EditorConfig.
• autoclose: Git History

  Pull request which should be auto-closed due to a messed-up Git history.
• autoclose: Project Conventions

  Pull request which should be auto-closed due to not following project conventions.
• autoclose: Spam

  Pull request which should be auto-closed as considered spam.
• autoclose: Stale

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

  Automated issue.
• automated-pr

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

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

  Pull requests adding or improving benchmarks for measuring performance.
• BLAS

  Issue or pull request related to Basic Linear Algebra Subprograms (BLAS).
• bot: Check Files

  Pull request needing an automated file check.
• bot: In Progress

  Pull request is currently awaiting automation.
• bot: Lint Autofix

  Pull request needing applicable lint errors to be automatically fixed.
• bot: Merge

  Pull request needing the latest project code be merged in.
• bot: Rebase

  Pull request needing to be rebased on the latest project code.
• bot: Update Copyright Years

  Pull request needing the copyright years of its files updated.
• Browser

  Issue or pull request specific to browser environments.
• Bug

  Something isn't working.
• C

  Issue involves or relates to C.
• CI

  Issue or pull request specific to continuous integration environments.
• ci: Skip

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

  Issue or pull request related to project dependencies.
• difficulty: 1

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

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

  Likely to be challenging but manageable.
• difficulty: 4

  Likely to be moderately difficult.
• difficulty: 5

  Likely to be difficult to implement with several unknowns.