Merge pull request #26 from xebia/3.3-Discussions

3.3 discussions

Author: Chukslord1

learn-pr/github/introduction-to-github/5-platform-management.yml

@@ -3,11 +3,11 @@ uid: learn.github.introduction-to-github.platform-management
 title: GitHub platform management
 metadata:
   title: GitHub platform management
-  description: In this unit, we're learning about how to manage your GitHub notifications, subscriptions, and how to publicize your project on GitHub pages.
+  description: Learn how to manage your GitHub notifications, subscriptions, and GitHub Pages to stay informed and organize your work efficiently.
   ms.date: 09/12/2024
   author: a-a-ron
   ms.author: aastewar
   ms.topic: unit
-durationInMinutes: 4
+durationInMinutes: 10
 content: |
   [!include[](includes/5-platform-management.md)]

learn-pr/github/introduction-to-github/includes/2-what-is-github.md

@@ -126,10 +126,48 @@ Now that we have a good understanding of repositories, we can review gists. Simi
 
 Every gist is a Git repository, which you can fork and clone and be made either public or secret. Public gists are displayed publicly where people can browse new ones as they’re created. Public gists are also searchable. Conversely, secret gists aren't searchable, but they aren’t entirely private. If you send the URL of a secret gist to a friend, they'll be able to see it.
 
+### Forking and cloning gists
+
+You can fork a gist to create a copy of someone else's gist in your account.
+
+1. Navigate to the gist you want to fork.
+2. Select **Fork** at the top-right of the gist page.
+
+To clone a gist locally:
+
+```bash
+git clone https://gist.github.com/your-gist-id.git
+```
+
 To learn more about gists, see the linked article in our Resources section at the end of this module titled *Creating Gists*.
 
+---
+
 ### What are wikis?
 
 Every repository on GitHub.com comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to share long-form content about your project, such as how to use it, how you designed it, or its core principles. While a README file quickly tells what your project can do, you can use a wiki to provide additional documentation.
 
 It’s worth a reminder that if your repository is private, only people who have at least read access to your repository will have access to your wiki.
+
+### Creating, editing, and deleting wiki pages
+
+You can use the GitHub wiki to create and manage documentation for your project.
+
+**To create a wiki page:**
+
+1. Navigate to the repository.
+2. Select the **Wiki** tab.
+3. Select **Create the first page** if no pages exist, or **New Page** to add a page.
+4. Enter a title and content, then select **Save Page**.
+
+**To edit a wiki page:**
+
+1. Navigate to the wiki page you want to edit.
+2. Select **Edit** at the top-right.
+3. Make changes and select **Save Page**.
+
+**To delete a wiki page:**
+
+- Deleting a wiki page requires using Git. Clone the wiki repository, remove the file, and push the change.
+
+Learn more about managing wikis in [GitHub Docs - Adding or editing wiki pages](https://docs.github.com/en/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages).

learn-pr/github/introduction-to-github/includes/4-collaborative-platform.md

@@ -102,3 +102,34 @@ Each category must have a unique name, emoji pairing, and a detailed description
 1. Select **Start discussion**.
 
 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.
+
+### Marking a comment as an answer
+
+In a Q&A style discussion, you can mark a comment as the accepted answer to the original question.
+
+1. Navigate to the discussion.
+2. Locate the comment that best answers the original question.
+3. Select **Mark as answer** below the comment.
+
+The comment will be highlighted, making it easy for others to find the solution quickly. You can also unmark an answer if needed.
+
+### Converting a discussion to an issue
+
+If a discussion leads to work that needs to be tracked, you can convert the discussion into an issue.
+
+1. Navigate to the discussion you want to convert.
+2. Select the **`...`** (three dots) menu at the top-right of the discussion.
+3. Select **Convert to issue**.
+4. Confirm the conversion and select a repository to create the new issue in.
+
+This keeps track of actionable work that originates from community conversations.
+
+### Pinning a discussion
+
+You can pin important discussions to the top of the Discussions page for better visibility.
+
+1. Navigate to the discussion you want to pin.
+2. Select the **`...`** (three dots) menu at the top-right of the discussion.
+3. Select **Pin discussion**.
+
+Pinned discussions are helpful for highlighting announcements, important questions, or ongoing topics the community should notice.

learn-pr/github/introduction-to-github/includes/5-platform-management.md

@@ -8,22 +8,54 @@ In this unit, we'll cover:
 
 ## Managing notifications and subscriptions
 
-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.
+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.
 
-### Subscription options
+You can subscribe to notifications for:
 
-You can choose to subscribe to notifications for:
+- Specific issues, pull requests, or gists
+- Repository activity like issues, pull requests, releases, or discussions
+- Workflow statuses for repositories using GitHub Actions
+- All activity across a repository
 
-- A conversation in a specific issue, pull request, or gist.
-- CI activity, such as the status of workflows in repositories set up with GitHub Actions.
-- Repository issues, pull requests, releases, security alerts, or discussions (if enabled).
-- All activity in a repository.
+You're automatically subscribed when you interact with conversations (commenting, opening an issue, being assigned), but you can also manually manage subscriptions as needed.
 
-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.
+If you're no longer interested in receiving updates, you can unsubscribe, unwatch, or customize the types of notifications you receive.
 
-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.
+## Subscribing to threads and finding threads where you're mentioned
 
-If you're ever interested in issues that mention a certain user, you can use *mentions:* as the qualifier to find those specific issues.
+Subscribing to individual threads, such as a particular issue or pull request, ensures you receive updates even if you weren't originally involved.
+
+You can subscribe to a thread by:
+
+- Selecting **Subscribe** on the right-hand sidebar of an issue, pull request, or discussion.
+
+To find conversations where you're mentioned:
+
+- Use the search qualifier `mentions:<username>` in the GitHub search bar to locate issues and pull requests where you were @mentioned.
+
+This makes it easy to keep track of discussions that require your input.
+
+### Filter notifications
+
+GitHub allows you to filter notifications using watch settings:
+
+- **Watching**: Receive notifications for all activity.
+- **Not watching**: Receive notifications only when you're participating or @mentioned.
+- **Ignore**: No notifications at all for a repository.
+- **Custom**: Fine-tune what types of activity (like pull requests, issues, or discussions) trigger notifications.
+
+You can manage watch settings by selecting **Watch** at the top of a repository page.
+
+### Configure notification settings
+
+You can configure where you receive notifications:
+
+- **Email**: Notifications delivered to your registered email address.
+- **Web**: Notifications viewed directly in your GitHub dashboard.
+- **Mobile**: Push notifications using the GitHub mobile app.
+- **Custom notifications**: Configure specific event types for different channels.
+
+Notification settings are managed under your GitHub account settings in **Notifications**.
 
 ## What are GitHub Pages?