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 collaborative platform documentation to include detailed instructions for marking comments as answers, converting discussions to issues, and pinning discussions. Enhanced clarity and usability with step-by-step guidance and visual references.
description: In this unit, we're learning about how to manage your GitHub notifications, subscriptions, and how to publicize your project on GitHub pages.
6
+
description: Learn how to manage your GitHub notifications, subscriptions, and repositories to stay informed and organize your work efficiently.
Copy file name to clipboardExpand all lines: learn-pr/github/introduction-to-github/includes/4-collaborative-platform.md
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,3 +102,34 @@ Each category must have a unique name, emoji pairing, and a detailed description
102
102
1. Select **Start discussion**.
103
103
104
104
That covers a little about how GitHub inspires collaboration. Now let's move to how you can manage notifications, subscribe to threads, and get started with GitHub pages.
105
+
106
+
### Marking a comment as an answer
107
+
108
+
In a Q&A style discussion, you can mark a comment as the accepted answer to the original question.
109
+
110
+
1. Navigate to the discussion.
111
+
2. Locate the comment that best answers the original question.
112
+
3. Select **Mark as answer** below the comment.
113
+
114
+
The comment will be highlighted, making it easy for others to find the solution quickly. You can also unmark an answer if needed.
115
+
116
+
### Converting a discussion to an issue
117
+
118
+
If a discussion leads to work that needs to be tracked, you can convert the discussion into an issue.
119
+
120
+
1. Navigate to the discussion you want to convert.
121
+
2. Select the **`...`** (three dots) menu at the top-right of the discussion.
122
+
3. Select **Convert to issue**.
123
+
4. Confirm the conversion and select a repository to create the new issue in.
124
+
125
+
This keeps track of actionable work that originates from community conversations.
126
+
127
+
### Pinning a discussion
128
+
129
+
You can pin important discussions to the top of the Discussions page for better visibility.
130
+
131
+
1. Navigate to the discussion you want to pin.
132
+
2. Select the **`...`** (three dots) menu at the top-right of the discussion.
133
+
3. Select **Pin discussion**.
134
+
135
+
Pinned discussions are helpful for highlighting announcements, important questions, or ongoing topics the community should notice.
Copy file name to clipboardExpand all lines: learn-pr/github/introduction-to-github/includes/5-platform-management.md
+42-10Lines changed: 42 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,22 +8,54 @@ In this unit, we'll cover:
8
8
9
9
## Managing notifications and subscriptions
10
10
11
-
You can choose to receive ongoing updates about specific activity on GitHub.com through a subscription. Notifications are the updates that you receive for specific activity to which you're subscribed.
11
+
Notifications help you stay up to date on important activity across your repositories and teams. Managing your subscriptions ensures you only get updates for the work that matters most to you.
12
12
13
-
### Subscription options
13
+
You can subscribe to notifications for:
14
14
15
-
You can choose to subscribe to notifications for:
15
+
- Specific issues, pull requests, or gists
16
+
- Repository activity like issues, pull requests, releases, or discussions
17
+
- Workflow statuses for repositories using GitHub Actions
18
+
- All activity across a repository
16
19
17
-
- A conversation in a specific issue, pull request, or gist.
18
-
- CI activity, such as the status of workflows in repositories set up with GitHub Actions.
You're automatically subscribed when you interact with conversations (commenting, opening an issue, being assigned), but you can also manually manage subscriptions as needed.
21
21
22
-
In some instances, you're automatically subscribed to conversations on GitHub. Examples include opening a pull request or issue, commenting on a thread, or being assigned to an issue or pull request.
22
+
If you're no longer interested in receiving updates, you can unsubscribe, unwatch, or customize the types of notifications you receive.
23
23
24
-
If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future.
24
+
## Subscribing to threads and finding threads where you're mentioned
25
25
26
-
If you're ever interested in issues that mention a certain user, you can use *mentions:* as the qualifier to find those specific issues.
26
+
Subscribing to individual threads, such as a particular issue or pull request, ensures you receive updates even if you weren't originally involved.
27
+
28
+
You can subscribe to a thread by:
29
+
30
+
- Selecting **Subscribe** on the right-hand sidebar of an issue, pull request, or discussion.
31
+
32
+
To find conversations where you're mentioned:
33
+
34
+
- Use the search qualifier `mentions:<username>` in the GitHub search bar to locate issues and pull requests where you were @mentioned.
35
+
36
+
This makes it easy to keep track of discussions that require your input.
37
+
38
+
### Filtering notifications
39
+
40
+
GitHub allows you to filter notifications using watch settings:
41
+
42
+
-**Watching**: Receive notifications for all activity.
43
+
-**Not watching**: Receive notifications only when you're participating or @mentioned.
44
+
-**Ignore**: No notifications at all for a repository.
45
+
-**Custom**: Fine-tune what types of activity (like pull requests, issues, or discussions) trigger notifications.
46
+
47
+
You can manage watch settings by selecting **Watch** at the top of a repository page.
48
+
49
+
### Configuring notification settings
50
+
51
+
You can configure where you receive notifications:
52
+
53
+
-**Email**: Notifications delivered to your registered email address.
54
+
-**Web**: Notifications viewed directly in your GitHub dashboard.
55
+
-**Mobile**: Push notifications using the GitHub mobile app.
56
+
-**Custom notifications**: Configure specific event types for different channels.
57
+
58
+
Notification settings are managed under your GitHub account settings in **Notifications**.
0 commit comments