How To Backlog

Issues

Issue is a "User story". It means a unit of work that has meaning by itself. Issues have labels. More info on how to work with issues can be found here:
https://guides.github.com/features/issues/

Backlog

Is a place where all of our work is done. Link to backlog can be found here:
https://github.com/Code2Gether-Discord/JokesOnYou/projects/1 We try to follow Agile flow, meaning which we have the following columns:

1. Backlog- all work that is to be done, but without any immediate plans. Issues, added to the project will end up here.
2. Sprint backlog- work to be done in 2 weeks span (current sprint), priority.
3. In progress- issues that are being worked on. Reopened issues and new PR will move here.
4. Review in progress- pull request raised, waiting for approvals, reviews. PR will move here when there is a single review done (but not all reviews needed yet)
5. Review approved- pull request completed. PRs will move here when approved others.
6. Done- merged to master, showed in a demo. PR will move here when merged to dev branch.

Pull Requests

When creating a PR, don't forget to link an issue with "#" symbol. Also, keep in mind to target dev and not master branch. Follow every change create a new branch. Follow this pattern:

docs/IssueNumber-docName- for documentation
feature/IssueNumber-featureName- for new features
bugfix/IssueNumber-bugfixName- for bugfixes
techdeb/IssueNumber-techDebtName- for refactoring
Describe what you did, what changes have you made.

At the end of every sprint (after review), dev branch gets merged to master.