Balmasexy opened a new issue, #35636:
URL: https://github.com/apache/beam/issues/35636

   > # :wave: Welcome to GitHub Learning Lab's "Introduction to GitHub"
   > 
   > To get started, I’ll guide you through some important first steps in 
coding and collaborating on GitHub.
   > 
   > :point_down: _This arrow means you can expand the window! Click on them 
throughout the course to find more information._
   > <details><summary>What is GitHub?</summary>
   > <hr>
   > 
   > ## What is GitHub?
   > 
   > I'm glad you asked! Many people come to GitHub because they want to 
contribute to open source 
<sup>[:book:](https://help.github.com/articles/github-glossary/#open-source)</sup>
 projects, or they're invited by teammates or classmates who use it for their 
projects. Why do people use GitHub for these projects?
   > 
   > **At its heart, GitHub is a collaboration platform.**
   > 
   > From software to legal documents, you can count on GitHub to help you do 
your best work with the collaboration and security tools your team needs. With 
GitHub, you can keep projects completely private, invite the world to 
collaborate, and streamline every step of your project.
   > 
   > **GitHub is also a powerful version control tool.**
   > 
   > GitHub uses Git 
<sup>[:book:](https://help.github.com/articles/github-glossary/#git)</sup>, the 
most popular open source version control software, to track every contribution 
and contributor 
<sup>[:book:](https://help.github.com/articles/github-glossary/#contributor)</sup>
 to your project--so you know exactly where every line of code came from.
   > 
   > **GitHub helps people do much more.**
   > 
   > GitHub is used to build some of the most advanced technologies in the 
world. Whether you're visualizing data or building a new game, there's a whole 
community and set of tools on GitHub that can get you to the next step. This 
course starts with the basics, but we'll dig into the rest later!
   > 
   > :tv: [Video: What is GitHub?](https://www.youtube.com/watch?v=w3jLJU7DT5E)
   > <hr>
   > </details><br>
   > 
   > <details><summary>Exploring a GitHub repository</summary>
   > <hr>
   > 
   > ## Exploring a GitHub repository
   > 
   > :tv: [Video: Exploring a 
repository](https://www.youtube.com/watch?v=R8OAwrcMlRw)
   > 
   > ### More features
   > 
   > The video covered some of the most commonly-used features. Here are a few 
other items you can find in GitHub repositories:
   > 
   > - Project boards: Create Kanban-style task tracking board within GitHub
   > - Wiki: Create and store relevant project documentation
   > - Insights: View a drop-down menu that contains links to analytics tools 
for your repository including:
   >   - Pulse: Find information about the work that has been completed and the 
work that’s in-progress in this project dashboard
   >   - Graphs: Graphs provide a more granular view of the repository activity 
including who contributed to the repository, who forked it, and when they 
completed the work
   > 
   > ### Special Files
   > 
   > In the video you learned about a special file called the README.md. Here 
are a few other special files you can add to your repositories:
   > 
   > - CONTRIBUTING.md: The `CONTRIBUTING.md` is used to describe the process 
for contributing to the repository. A link to the `CONTRIBUTING.md` file is 
shown anytime someone creates a new issue or pull request.
   > - ISSUE_TEMPLATE.md: The `ISSUE_TEMPLATE.md` is another file you can use 
to pre-populate the body of an issue. For example, if you always need the same 
types of information for bug reports, include it in the issue template, and 
every new issue will be opened with your recommended starter text.
   > 
   > <hr>
   > </details>
   > 
   > ### Using issues
   > 
   > This is an issue 
<sup>[:book:](https://help.github.com/articles/github-glossary/#issue)</sup>: a 
place where you can have conversations about bugs in your code, code review, 
and just about anything else.
   > 
   > Issue titles are like email subject lines. They tell your collaborators 
what the issue is about at a glance. For example, the title of this issue is 
Getting Started with GitHub.
   > 
   > 
   > <details><summary>Using GitHub Issues</summary>
   > 
   > ## Using GitHub issues
   > 
   > Issues are used to discuss ideas, enhancements, tasks, and bugs. They make 
collaboration easier by:
   > 
   > - Providing everyone (even future team members) with the complete story in 
one place
   > - Allowing you to cross-link to other issues and pull requests 
<sup>[:book:](https://help.github.com/articles/github-glossary/#pull-request)</sup>
   > - Creating a single, comprehensive record of how and why you made certain 
decisions
   > - Allowing you to easily pull the right people and teams into a 
conversation with @-mentions
   > 
   > :tv: [Video: Using issues](https://www.youtube.com/watch?v=Zhj46r5D0nQ)
   > 
   > <hr>
   > </details>
   > 
   > <details><summary>Managing notifications</summary>
   > <hr>
   > 
   > ## Managing notifications
   > 
   > :tv: [Video: Watching, notifications, stars, and 
explore](https://www.youtube.com/watch?v=ocQldxF7fMY)
   > 
   > Once you've commented on an issue or pull request, you'll start receiving 
email notifications when there's activity in the thread.  
   > 
   > ### How to silence or unmute specific conversations
   > 
   > 1. Go to the issue or pull request
   > 2. Under _"Notifications"_, click the **Unsubscribe** button on the right 
to silence notifications or **Subscribe** to unmute them
   > 
   > You'll see a short description that explains your current notification 
status.
   > 
   > ### How to customize notifications in Settings
   > 
   > 1. Click your profile icon
   > 2. Click **Settings**
   > 3. Click **Notifications** from the menu on the left and [adjust your 
notification 
preferences](https://help.github.com/articles/managing-notification-delivery-methods/)
   > 
   > ### Repository notification options
   > 
   > * **Watch**: You'll receive a notification when a new issue, pull request 
or comment is posted, and when an issue is closed or a pull request is merged  
   > * **Not watching**: You'll no longer receive notifications unless you're 
@-mentioned
   > * **Ignore**: You'll no longer receive any notifications from the 
repository
   > 
   > ### How to review notifications for the repositories you're watching
   > 
   > 1. Click your profile icon
   > 2. Click **Settings**
   > 3. Click **Notification** from the menu on the left
   > 4. Click on the [things you’re watching](https://github.com/watching) link
   > 5. Select the **Watching** tab
   > 6. Click the **Unwatch** button to disable notifications, or **Watch** to 
enable them
   > 
   > <hr>
   > </details>
   > 
   > <hr>
   > <h3 align="center">Keep reading below to find your first task</h3>
   > 
   
   
   
   _Originally posted by @Balmasexy in 
https://github.com/smsalman75/github-slideshow/issues/1#issuecomment-3095581983_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscr...@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to