ckeditor
Added checklist to PR template.
Suggested merge commit message (convention)
Internal: Adds checklists to pull request template.
Additional information
Let's just start using this checklist and see where we get.
I choose those questions, because they should (IMO) increase self-awareness of the PR's impact. There are many other possibilities: tips for reviewers, checks for common issues (style, readability, test quality, etc.), but I have the feeling this would be too much for now (I'm waiting for comments about that).
PR Scope
- [ ] Is there any breaking change?
- [ ] Is there any new feature?
- [ ] Is there any new API?
- [ ] Was any architectural decision made during or before the implementation?
- [ ] If there is any breaking change, has it been discussed and approved?
- [ ] If there is any new feature, has it been documented?
- [ ] If there is any new API, has it been documented and announced?
- [ ] If there was any architectural decision made, has an ADR (Architectural Decision Record) been created?
Quality check
- [ ] Was an automated test added to guard against regression (that would have failed with the previous code)?
- [ ] Does the change negatively impact the performance of existing features?
- [ ] Are there any todos left in this PR that require follow-up tickets?
- [x] Have this PR been self-reviewed by the author?
There has been no activity on this PR for the past year. We've marked it as stale and will close it in 30 days. We understand it may still be relevant, so if you're interested in the contribution, leave a comment or reaction under this PR.
We've closed your PR due to inactivity. While time has passed, the core of your contribution might still be relevant. If you're able, consider reopening a similar PR.