You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update documentation to include additional search and organization features in repository history. Add quiz questions and enhance documentation on milestones, labels, saved replies, and assignees.
Copy file name to clipboardExpand all lines: learn-pr/github/search-organize-repository-history-github/includes/2-search-organize-repository-history-github.md
+107-1Lines changed: 107 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
Here, we'll discuss how you can use filters, blame, and cross-linking to search and organize repository history.
1
+
Here, we'll discuss how you can use filters, blame, cross-linking, labels, milestones, saved replies, and assignees to search and organize repository history.
2
2
3
3
Put yourself in the position of a developer who has just joined a large project. Someone just posted a new issue reporting a bug related to the web app's sidebar, and you've been assigned to fix it. You've already read through the report a few times and understand the problem being described, so now you need to figure out how to get started with the fix.
4
4
@@ -50,6 +50,68 @@ Query|Explanation
50
50
51
51
Learn more about [Understanding the search syntax](https://docs.github.com/enterprise-cloud@latest/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax?azure-portal=true)
52
52
53
+
## Using Milestones
54
+
55
+
Milestones let you group issues and pull requests into shared goals, like a sprint, a product release, or a project phase.
56
+
57
+
### Create a milestone
58
+
59
+
1. Navigate to the Issues tab of your repository.
60
+
2. Select Milestones from the top menu.
61
+
3. Click New milestone.
62
+
4. Enter a title, description, and optionally a due date.
63
+
5. Click Create milestone.
64
+
65
+
### Assign a milestone to an issue or pull request
66
+
67
+
1. Open any issue or PR.
68
+
2. In the right sidebar, select Milestone.
69
+
3. Choose from the list of available milestones.
70
+
71
+
When you view a milestone, GitHub shows how many issues/PRs are complete and how many remain—making it a helpful planning and tracking tool.
72
+
73
+
> You can filter by milestone in GitHub Projects or with advanced search queries like:
74
+
>
75
+
> ```
76
+
> is:open is:pr milestone:"Release v1.0"
77
+
> ```
78
+
79
+
Milestones work best when used consistently across your team's planning workflow.
80
+
81
+
## Labels and Milestones in Search
82
+
83
+
Labels and milestones are metadata tools that help teams organize issues and pull requests. They also improve the accuracy of search queries.
84
+
85
+
### Filter by label
86
+
87
+
You can narrow down issues by filtering with the `label:` keyword.
88
+
89
+
For example:
90
+
91
+
```
92
+
is:open is:issue label:bug
93
+
```
94
+
95
+
This returns all open issues labeled as "bug." Labels can reflect issue type, priority, team, or workflow status.
96
+
97
+
> Tip: You can combine labels with other filters for precise queries, such as:
98
+
>
99
+
> ```
100
+
> is:pr label:"ready for review" author:@me
101
+
> ```
102
+
103
+
### Filter by milestone
104
+
105
+
Milestones help you group issues and pull requests toward a target release or goal. Use the `milestone:` keyword in your query to return items within a specific milestone.
106
+
107
+
For example:
108
+
109
+
```
110
+
is:open is:issue milestone:"Sprint 1"
111
+
```
112
+
113
+
> Note: Only open milestones will match unless you include closed ones by searching with `milestone:*`.
114
+
53
115
## What is git blame?
54
116
55
117
Despite its ominous name, `git blame` is a command that displays the commit history for a file. It makes it easy for you to see who made what changes and when. This makes it much easier to track down other people who have worked on a file in order to seek out their input or participation.
@@ -69,6 +131,50 @@ In our scenario, there are a few ways you might get to this view. You might've f
69
131
70
132
Part of what makes GitHub great for collaborative software projects is its support for linking disparate pieces of information together. Some of this happens automatically, such as when you create a pull request from a series of commits on a branch. Other times, you can use the interface to manually link pull requests or projects to issues using the dropdown options.
71
133
134
+
## Saved replies
135
+
136
+
Saved replies let you quickly respond to issues and pull requests with prewritten messages. They’re especially helpful for project maintainers who often give the same feedback or instructions.
137
+
138
+
### Create or edit a saved reply
139
+
140
+
1. Click your profile photo in the top right corner and select Settings.
141
+
2. In the left sidebar, click Saved replies.
142
+
3. Select New saved reply.
143
+
4. Enter a title and your message.
144
+
5. Click Save reply.
145
+
146
+
To edit or delete a saved reply, return to the Saved replies settings and use the options beside each one.
147
+
148
+
## Using a saved reply
149
+
150
+
When writing a comment on an issue or pull request, you can insert a saved reply:
151
+
152
+
1. Click the comment box.
153
+
2. Select the Insert a saved reply icon (speech bubble with lines).
154
+
3. Choose a saved reply from the list.
155
+
4. Modify the text if needed, then click Comment.
156
+
157
+
Saved replies save time and help ensure consistency when responding across your project.
158
+
159
+
## Adding assignees
160
+
161
+
You can assign one or more people to an issue or pull request to show who’s responsible for working on it.
162
+
163
+
### Add an assignee
164
+
165
+
1. Open the issue or pull request.
166
+
2. In the right sidebar, click Assignees.
167
+
3. Select one or more users from the dropdown.
168
+
169
+
You can also assign people directly from the list view using the checkboxes beside each issue and selecting Assign from the top bar.
170
+
171
+
> Tip: Use the `assignee:` filter in your searches to find items assigned to yourself or others.
172
+
173
+
Example:
174
+
```
175
+
is:open is:issue assignee:@me
176
+
```
177
+
72
178
### Autolinked references
73
179
74
180
To make it even easier to cross-link different items throughout your project, GitHub offers a shorthand syntax. For example, if you leave a comment like `Duplicate of #8`, GitHub will recognize that #8 is an issue and create the appropriate link for you.
Copy file name to clipboardExpand all lines: learn-pr/github/search-organize-repository-history-github/includes/5-summary.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,9 @@ You learned about:
5
5
- Finding relevant issues and pull requests.
6
6
- Searching history to find context.
7
7
- Making connections within GitHub to help others find things.
8
+
- Use labels and milestones to filter and organize issues.
9
+
- Respond faster with saved replies.
10
+
- Assign issues and pull requests to collaborators.
8
11
9
12
Now that you're familiar with finding and organizing information on GitHub, learn to [Maintain a secure repository by using GitHub best practices](/training/modules/maintain-secure-repository-github/).
0 commit comments