Skip to content

No labels!

There aren’t any labels for this repository quite yet.

flag: (beta)
flag: (beta)
flag: 💥 Breaking change
flag: 💥 Breaking change
This PR contains breaking changes and should not be merged
flag: don't merge
flag: don't merge
This PR should not be merged at the moment
flag: merge pending release
flag: merge pending release
Pending Strapi Release
flag: migration guide
flag: migration guide
This PR introduces changes that require a migration guide
good first issue
good first issue
Good task for newcomers to the repo
hacktoberfest-accepted
hacktoberfest-accepted
PR is accepted and counts towards hacktoberfest
internal
internal
PRs created by the Strapi core team
issue: added to backlog
issue: added to backlog
issue: bug
issue: bug
issue: discussion
issue: discussion
issue: doc request
issue: doc request
Issues that require adding new content, possibly with some prior research
issue: docs/code example
issue: docs/code example
Issues about incorrect code examples found on docs.strapi.io
issue: docs/instructions
issue: docs/instructions
Issues about incorrect instructions found on docs.strapi.io
issue: docs/screenshot
issue: docs/screenshot
Issues about incorrect screenshots found on docs.strapi.io
issue: docs/ux
issue: docs/ux
UX/UI Issues found on docs.strapi.io
issue: not docs
issue: not docs
issue: quick fix
issue: quick fix
Issues that could be fixed quickly, with small- to medium-sized PRs
issue: seo
issue: seo
SEO-related issues
pr: code fix
pr: code fix
PRs only fixing existing code examples
pr: feature release
pr: feature release
(Was this backported from strapi/strapi PRs? We use "pr: new content" instead.)
pr: fix
pr: fix
Used on the docs repo for anything that is not "new" or "updated" content: chore, typos, fixes, etc.
pr: new content
pr: new content
PRs for new product features or new documentation sections
pr: security notice
pr: security notice
pr: typo
pr: typo
PRs only fixing typos in the text instructions (excl. code samples, use "pr: code fix" instead)
pr: updated content
pr: updated content
PRs updating existing documentation content
severity: critical
severity: critical
If the issue has a security impact or breaks core usage of the product
severity: high
severity: high
If it breaks the basic use of the product
severity: low
severity: low
If the issue only affects a very niche base of users and an easily implemented workaround can solve