[ ] e. Used guards (middleware) where necessary and tested if route is guarded.
4. If relevant, test these browsers
[ ] a. Chrome
[ ] b. Firefox
[ ] c. Opera
[ ] d. Edge
[ ] e. Safari
PR Rules 1. Add relevant labels. 2. Select at least two reviewers. 3. Assign all reviewers allowed to merge the branch, including yourself. 4. If relevant to the sprint, put related issue in 'Awaiting Approval' column on project board. 5. Add to the corresponding milestone.
Reviewer info 1. You can use aliases to refer to specific PR checklist items. For example 'Hey @JohnDoe, for this line please check 3.a and 1.d.' 2. Where possible, please use the suggestions feature in github so the author has a better idea of the solution you had in mind.
This form should be filled in by the author of this PR.
closes #XXX
What is it supposed to do
All kinds of changes for deployment. Most of them are described on the live seaqull build. https://seaqull.com/posts/ea2d843a-5f71-49d3-a811-3be4dded9737
Nearly all changes are described in the commits.
How can we test your branch
https://seaqull.com/posts/ea2d843a-5f71-49d3-a811-3be4dded9737
Additional notes
Things to keep in mind regarding the PR that don't fit in the previous two headings.
1. General checklist
2. If relevant, front-end checklist
3. If relevant, back-end checklist
4. If relevant, test these browsers
PR Rules
1. Add relevant labels.
2. Select at least two reviewers.
3. Assign all reviewers allowed to merge the branch, including yourself.
4. If relevant to the sprint, put related issue in 'Awaiting Approval' column on project board.
5. Add to the corresponding milestone.
Reviewer info
1. You can use aliases to refer to specific PR checklist items. For example 'Hey @JohnDoe, for this line please check 3.a and 1.d.'
2. Where possible, please use the suggestions feature in github so the author has a better idea of the solution you had in mind.