Issues in GitHub

An Issue in GitHub is a sort of bug tracker for a project which has its own section in every repository. It can be used for discussions which include a variety of things like reporting a bug on that repository, asking questions or even asking for a particular feature. It is a great place to keep a track of tasks and enhancements of the project. Being good at writing issues often helps in building better open source projects and will help other contributors to understand your project better and help you.

To make a new issue in your repository, navigate to the repository where you want to raise an issue and go to the Issues tab as shown below:

After navigating to the issues tab, click on New Issues to create an Issue for your project as shown below:


Then give a suitable heading and detailed information about the issue. As an example, let us take a look at angular repository which is a web framework:



Features of Issues

An issue contains the following entities:

  • A title and a description which clearly explains what the issue is about. It should be concise and should be clear to understand.
  • Color-coded labels that help to filter out specific issues for you. This is similar to the categorization we see in emails. An issue can have more than one label and can be filtered out by one or many labels at a time. An issue with labels looks like this:
  • Milestones help to track issues and merge requests to achieve a broader goal in a certain duration of time. They can be visualized as containers for specific type of issues. These can be of various types for example:
    • Version 1.0 – For a specific release of a software version.
    • Beta Launch – File bugs that you need to fix before you’ll launch the beta version of your project.
    • March Due – File issues that you’d like to work in March.
    • Redesign – Issues related to the design of your project.

    If you are not able to set milestone, that is because you do not have the permissions. This can be resolved only when the repository owner makes you a contributor.

  • An assignee, who is responsible to work on a specific issue at a time and to take the issue forward. They are also assigned by the repository owner.
  • Comments which can be done by anyone who has an access to the repository.

Some other useful features in issues are:

  • @mention – A great way to reference other users within GitHub is using the @mention feature. To notify other users of a particular issue and to seek help or guidance from them, tag them by using @username which sends them a notification to look into the issue and contribute to it. It can also be used to notify teams rather than individuals, in which all the team members will be notified.
  • References – Sometimes some issues are dependent on other issues. These issues can be referenced by placing a # in front of issue_number of the other issue which is dependent on the current issue and prefacing the commits with “Fixed”, “Fixes”, “Closed”, “Closes” or “Close”.
  • Searches – At the top-right in the issues section, there is a search box which lets you search through the issues present. Issues can be searched on the basis of keywords, states or assignees.

Finally, there is an issue dashboard which lists all your issues from all the projects you’ve been working on and includes:

  • All issues in repositories you own and collaborate in.
  • Issues that are assigned to you.
  • Issues that you have created.
My Personal Notes arrow_drop_up

Check out this Author's contributed articles.

If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to contribute@geeksforgeeks.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.

Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.


Article Tags :

3


Please write to us at contribute@geeksforgeeks.org to report any issue with the above content.