mirror of
https://github.com/strapi/strapi.git
synced 2025-06-27 00:41:25 +00:00
Page:
Home
Pages
Create files on Heroku
Deploy on Heroku
Frequently Asked Questions
Home
Migration guide alpha.10 to alpha.11
Migration guide alpha.11 to alpha.12
Migration guide alpha.12.1 to alpha.12.2
Migration guide alpha.12.2 to alpha.12.3
Migration guide alpha.12.3 to alpha.12.4
Migration guide alpha.12.4 to alpha.12.5
Migration guide alpha.12.5 to alpha.12.6
Migration guide alpha.12.6 to alpha.12.7
Migration guide alpha.12.7 to alpha.13
Migration guide alpha.13 to alpha.13.1
Migration guide alpha.13.1 to alpha.14
Migration guide alpha.14 to alpha.14.1
Migration guide alpha.14.1 to alpha.14.2
Migration guide alpha.14.2 to alpha.14.3
Migration guide alpha.14.3 to alpha.14.4
Migration guide alpha.14.4 to alpha.14.5
Migration guide alpha.14.5 to alpha.15
Migration guide alpha.15 to alpha.16
Migration guide alpha.7.4 to alpha.8
Migration guide alpha.8 to alpha.9
Migration guide alpha.9 to alpha.10
Migration guide
Switch from dev app to prod
Clone
10
Home
DMehaffy edited this page 2018-11-14 08:22:55 -07:00
Table of Contents
API creation made simple, secure and fast.
The most advanced open-source Content Management Framework to build powerful API with no effort.
Labels description:
PR's labels:
flag: 💥 Breaking change
- If an update breaks generated API of an application configuration (if replacing plugins and admin is not enough to apply the update to an existing application)
Define the type of the PR (apply just one of these):
pr: 🐛 Bug fix
pr: 💅 Enhancement
pr: 🚀 New feature
Define where the PR apply main changes (apply just one of these):
source: Admin
source: Documentation
source: Framework
source: Plugin
⚠️ All these labels have to be carefully assign cause they are automatically used to generate the change log for a new release
Issue's labels:
Define the type of the issue (apply just one of these):
type: bug 🐛
- If it breaks the product or is not a finished featuretype: discussion ✍️
- If we have to discuss about a topic before work is started on the issuetype: documentation 📖
- If an update has to be done in the documentationtype: enhancement 💅
- If it's an update of the UI or UXtype: feature request 🙏
- If it is a new feature requested by a usertype: help wanted 🤷♂️
- If the issue is a not directly concerning Strapi or it's a mistake of the usertype: question 🙋
- When a user has a question
Define the priority:
priority: critical
- If the issue as a security impact or break core usage of the productpriority: high
- If it break the basic use of the product (not usable)priority: medium
- If we plan to work on or if it's betweenhigh
andlow
definition.priority: low
- If we not plan to work on, typically good for new contributors to work on
⚠️Only apply
priority
label if the issue is abug
type.
Define the status:
status: can't reproduce
- If we are not able to reproduce with the same Strapi, Node and Npm versionstatus: confirmed
- If the issue is validstatus: duplicate
- If the issue is a duplicate, in this case: Apply this label, send the link of the other issue and close.status: have to reproduce
- It's a kind of reminder to test the issue - basically if we read the issue and haven't time to test it.status: need informations
- If the issue have missing information or it's not completely clear what the issue is.
⚠️Only apply
priority
label if the issue is abug
type.
Strapi Docs