General GitHub project Workflow for ZeroWaste

General Workflow

1. QC or Developer creates User Story from Repository Issues, without adding it directly to the Project Board. More about the issue structure
2. The team and Tech Expert must then consider the issue, then move to “Backlog” or close with a comment.
3. The Developer can assign themselves to the Issue from the “Backlog”, move it to the “In Progress” and start working on it.
4. After the Developer resolves the issue, they open a Pull Request to the Develop branch. More about Pull Requests

Do not forget to set base:main to base:develop before creating PR.

5. The developer should assign themselves to this Pull Request and link it to any relevant User Stories and Dev Tasks. Once completed, the linked issues on the Project board must be moved from "In Progress" to "Ready for Review."

6. The Pull Request must pass all automated checks and be peer-reviewed and approved by at least one team member and the Tech Expert.

7. After receiving two approving reviews (from a team member and the Tech Expert) and resolving possible Merge Conflicts, the Developer can Merge the working branch to the Develop branch, then delete the current branch. More about Merge Conflicts

8. After a successful merge, the linked User Story (Dev Task) must be moved from "Ready for Review" to "Ready for QA". If the quality control team (QC) detects any insufficiency in the bug fix or new functionality to meet the requirements, the QC and developer must work together to resolve the differences.In order to do this, QC team member assings 'Rejected by QC' label to the issue and leaves comment what`s wrong in it. After that labeled issue must be moved from "Ready to QA" to "Rejected" on the Project board. Developer move rejected issue to "In Progress" and start resolving problem. Steps 4-7 of General Workflow are repeated and issue return to "Ready for QA" for confirmation testing by QC team and validation.

9. User Story (Dev Task, Bug Report) which has passed the test execution and has closed like compleated by QC team member moves to "Ready to Deploy" automatically.

Creating an Issue

• QC or Developer can create a new issue from Milestone. More about the issue structure User Story can be as small as needed, if the functionality described is too big, consider creating Epic and then dividing it into smaller User Stories. In the User Story template, there is a Tasks subsection, so you can split the story into smaller pieces if needed.

• The Tasks can be converted to a separate issue, so when you create a Pull Request you should link it both to the User Story and Task issue.

• It is recommended to use the Dev Task Label for such issues.

• Also, if under the current Issue or PR, there is a comment/suggestion that requires creating a separate issue/PR to resolve it, you can select Reference in a new issue.

• This will create an issue with the comment reference. Create a descriptive title and add a detailed description to the Body.

Creating an Issue by QC

QC has to create a new issue from Milestone. More about Milestones please find here

Step 1. Choose appropriate Milestone from the list of Milestones

Step 2. Click ‘New Issue’ button

Step 3. Choose ‘Bug report’ -> ‘Get started’ button

Step 4. QC creates new issue without adding it directly to the Project Board and without assignee. Developer can assign themselves to the Issue from the “Backlog”, move it to the “In Progress” and start working on it. All the necessary information should be filled in the Bug report:

Step 5. Paste any additional information (video or photo) in order to describe current issue in more detail

Step 6. Click ‘Submit new issue’ button

Please see an example

In case there are any issues that are related to newly created issue please note this information in the comment and link it to any relevant issue:

---