AjobK / Seaqull

Seaqull programming blog
http://www.seaqull.com
3 stars 0 forks source link

347 refactor desktop menu #357

Closed AjobK closed 2 years ago

AjobK commented 2 years ago

closes #XXX


What is it supposed to do
Explain in short what your PR is for


How can we test your branch
Explain how can test your branch as specifically as possible. Mention the page, button, etc. (For back-end route, function, etc.)


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.


This form should be filled in by the author of this PR.