Skip to main content

GitKit (2nd ed.) Learn git and GitHub in Context

Grant Braught, Lori Postner, Darci Burdge, Ruth Lamprecht, Stoney Jackson, Karl R. Wurst

Section 2.5 The Issue Tracker

FOSS projects often use an issue tracker to maintain a list of bugs to be fixed, features to be added and other tasks to be completed. Thus, the issue tracker is a good place to go in order to find something to work on in a FOSS project. The exercises in this section will guide you through interaction with the GitKit FarmData2 issue tracker as shown in Figure 2.5.1. By the end of the section you will have found an issue to work on.
🔗
The GitHub issue tracker displaying issues from the GitKit FarmData2 repository.
Figure 2.5.1. The GitKit FarmData2 issue tracker in GitHub.
🔗
🔗

Subsection 2.5.1 Exploring the Issue Tracker

Exercises

1.
The tasks in this exercise will help you to find the issue tracker for the GitKit FarmData2 repository that you will be using.
🔗
(a)
Visit the URL that your instructor provided for the GitKit FarmData2 repository that you will be using as the upstream repository for your course.
🔗
🔗
(b)
Click the "Issues" tab near the top of the page to go to the issue tracker. This will take you to a page similar to the one shown in Figure 2.5.1.
🔗
🔗
🔗
2.
Use the issue tracker in the GitKit FarmData2 repository to complete the following tasks.
🔗
(a)
Every issue has a number and a title. What is the title of issue #10?
🔗
  • Add Missing "that"
    🔗
  • Correct!
  • Seeding Report: Allows Invalid Inputs
    🔗
  • That is not the correct title.
  • Seeding Input: Duplicates appearing in Area Dropdown
    🔗
  • That is not the correct title.
  • Dickinson College Farm Link
    🔗
  • That is not the correct title.
Hint.
Be sure you are looking at issue #10.
🔗
🔗
🔗
(b)
Each issue can have tags that can be used to sort and categorize issues. Select all of the tags that are associated with issue #8?
🔗
  • Image of the Documentation label.
  • Image of the Round1 label.
  • Image of the Enhancement label.
  • Image of the Typos label.
  • Image of the Bug label.
  • Image of the UI/UX label.
Hint.
Be sure you are looking at the correct issue tracker and that you are looking at issue #8.
🔗
🔗
🔗
(c)
Which file in the repo would you need to modify in order to fix the typo described in issue #11?
🔗
  • ONBOARDING.md
  • Correct!
  • INSTALL.md
  • Be sure you are looking at issue #11.
  • CONTRIBUTING.md
  • Be sure you are looking at issue #11.
  • LICENSE.md
  • Be sure you are looking at issue #11.
Hint.
Be sure you are looking at the correct issue traker and that you are looking at issue #11.
🔗
🔗
🔗
(d)
Which of the following indicates an order by which the issues can be sorted?
🔗
  • Newest
  • Oldest
  • Most recently updated
  • Has the greatest number of comments
  • Most difficult
  • Highest priority
Hint.
Find the sort drop-down (which will be headed either "Newest" or "Oldest" depending on how it was last set) in the issue tracker and see what sort by options are available. Answers are not an exact match.
🔗
🔗
🔗
(e)
Hint.
Choose the best match.
🔗
🔗
🔗
🔗
🔗
🔗

Subsection 2.5.2 Claiming an Issue

Because projects often have many people working asynchronously many will have a process by which contributors can claim an issue that they are interested in working on and have that issue assigned to them in the issue tracker.
🔗
The following exercises will guide you through the process of claiming an issue to work on in the GitKit FarmData2 issue tracker.
🔗

Exercises

1.
Examine the GitKit FarmData2 issue tracker. How can you tell which issues have already been assigned?
🔗
  • The avatar of the assigned user appears to the right of the issue title.
  • Correct!
  • The issue no longer appears in the issue tracker.
  • A list of issues should appear. Be sure you are looking at the issue tracker for FarmData2.
  • The username of the assigned user appears next to the issue title.
  • The username does not appear next to the title.
  • The issue is moved to a separate list of assigned issues.
  • There is no separate list. Make sure there are no filters set.
  • The issue tracker does not show any indication that an issue has been assigned.
  • Make sure you are looking to the right of the title.
Hint.
Look for some lines for issues that look different than the others and hover your mouse over the different parts.
🔗
🔗
🔗
In the GitKit FarmData2 issue tracker, contributors interested in working on an issue can request that it be assigned to them by commenting on the issue with the exact message:
🔗
I would like to work on this please!
🔗
The first person who comments on an unclaimed issue with this message will receive a response from the project maintainers. This messages will indicate that the issue has been assigned to them and the issue tracker will update to show this as you saw in Exercise 2.5.2.1.
🔗
2.
(b)
Comment on the issue that you chose using the message above to claim it.
🔗
Hint.
Click on the issue title to open the issue and use the "Add a comment" box at the bottom of the page.
🔗
Remember you must type the message exactly as shown.
🔗
🔗
🔗
(c)
Reload the issue tracker and check that you received a response and that the issue has been assigned to you.
🔗
Hint.
If you did not receive a response, wait a few minutes and reload the issue tracker page again. Sometimes it takes a few minutes for your comment to be noticed and the issue to be assigned. If you still do not receive a response check that you typed the message correctly.
🔗
If you received a response telling you that you were not assigned the issue, someone else slipped a comment in just ahead of you and was assigned the issue. If this happens, just try Task 2.5.2.2.b again.
🔗
🔗
🔗
🔗
3.
Give the full URL to the issue that you have been assigned, for example https://github.com/my-class/GitKit-FarmData2/issues/2
🔗
🔗
4.
It is worth noting that different projects will have different processes for claiming and assigning issues, and some projects may not assign issues at all. What are some advantages and disadvantages of assigning issues to specific individuals?
🔗
Select each of the statements that describe an advantage of assigning issues.
🔗
  • To prevent wasting effort by having two developers work on the same issue.
    🔗
  • Allow a developer to "hold on" to an issue, even if they are not currently working on it.
    🔗
  • To plan in advance who will be working each issue.
    🔗
Hint.
Think about this from both the individual developer’s perspective and from the overall project’s perspective.
🔗
🔗
🔗
🔗
🔗
You have attempted of activities on this page.
🔗
PrevTopNext