## 🦺 Issue and Pull Request Requirements

### Issue Formatting:

Issue title should start with the Module name, for example `[Analytics Module/Feature]: Issue Text` 

For example the issue name is `[Elementor/Blockquote]: Add new blockquote widget` which generate the id `43`.

### Pull Request Formatting

**Note:** Before creating a new branch for any issue, make sure the issue is created, if not please create it before creating a new branch and PR

- Branch slug format should be `fixed-{issueId}` e.g. `fixed-43`
- PR Title should start with the `Fixed #{issueId}: Issue Title` E.g. For above issue the pr title should be `Fixed #43: Add new blockquote widget`
- In PR description area add the text [ `Closes #{issueId}`]
- Make sure at least 1 reviewer, Project and Milestone are added
- PR author should self-assign that PR to themself
- If related PR is present in the PRO repo, don't forget to mention it in the description area. Ex: `Related PR in the PRO repo: PRLink`

### Merging
- PR should not be merged without minimum 1 approvals
- If you think PR might affect the plugin security(even if a small possibility), then add the `Security Review Needed` label to that PR
- Once the security review is done, the reviewer will remove that security-related label
- If PR is invalid, before closing it, add the appropriate label `invalid` or `won't merge` along with the appropriate comment

## 🏘️ Versioning
- For Versioning, we use this formatting **1.0.major.patch**, example 1.0.53.1
- Each major version will have its own Project with all the issues included for that sprint.
- Same Project will have columns for the patch releases 
- Once the next major version is released, move the rest of the remaining issues to the next sprint and close that Project