Using GitHub issues

GitHub issues is more of a common board where GitHub users or members of the project can document the progress, report any bugs or suggest any improvements needed. When working with a team it is probably the best way to track progress and keep everyone updated.

It is also not limited as you can add issues to other user’s repo, to report bugs or suggest an idea.

👩‍💻Adding issues to repositories

We will jump straight into the steps of adding issues to a repo.

1. Open the repo you want to add an issue to.
2. Next to the code section on the repo you can find issues, open it.

3. To create a new issue click on the new issue button.

4. In the new issue add a title and express your concern or improvements that you think is necessary.

5. The write section is where we can elaborate on our issues. The text can be edited using the various options on the top right panel .

😉Cool features available in issues

1. On the editing section you can format the text, add links, code or quoted text, you can also add a numbered, bulleted or checked lists.

2. One can be able to tag someone in the text, reference an issue or text.

3. In the furthest right row, we can specify certain attributes such as who to assign the work to, the issues label, reference a project or pull requests and also one can view milestones taken to solve the issue.

❓❔Why use it?

Using issues for an organized team is necessary as it has various features that help smoothen out various things. Using it makes it easier to focus on important tasks and keeps your works and plans in one place.

You can create two repositories, one for code and another for issues to tack user stories then link them. You can restrict permission to the code repository keeping it private but using the issues to keep track of it publicly. This increases the number of commits and repos as a junior dev.

Thank you for reading!!