Sample form for GitHub actions issue 16

[aadilahmed]

Title

issue 16

Is there a dependency?

Yes

If Yes, please explain

No response

Overview

test move-closed-issues.yml

Checks

• An issue containing only 'role: back end' and 'role: front end' labels closes -> UAT.
• An issue containing only 'role: front end' closes -> UAT.
• An issue containing only 'Feature: Refactor CSS', 'Feature: Refactor JS / Liquid', and 'P-Feature: Home page' -> Done.
• An issue containing no label -> UAT
• Make sure the labels are placed in the code in such a way that we can easily add, edit, or delete labels
• The columns id should ideally be a secret, so that they are not exposed. When the id is found, please consult an admin to add it to our secrets. Columns id can be retrieved as a link, from the columns settings menu, for example . Please retrieve the id from there.
• In the PR, request the reviewer to, after merging, test that the board automation does not intercept or supercede this GHA. If so, the team leads will need to remove the default automation to allow this one to work.

Create new GHA

• This is to create a new GHA Start here!

[github-actions]

Hi @aadilahmed.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels