Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting Started with GitHub #1

Closed
github-learning-lab bot opened this issue Jun 4, 2019 · 5 comments

Comments

Projects
None yet
1 participant
@github-learning-lab
Copy link

commented Jun 4, 2019

馃憢 Welcome to GitHub Learning Lab's "Introduction to GitHub"

To get started, I鈥檒l guide you through some important first steps in coding and collaborating on GitHub.

馃憞 This arrow means you can expand the window! Click on them throughout the course to find more information.

What is GitHub?

What is GitHub?

I'm glad you asked! Many people come to GitHub because they want to contribute to open source 馃摉 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 馃摉, the most popular open source version control software, to track every contribution and contributor 馃摉 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!

馃摵 Video: What is GitHub?



Exploring a GitHub repository

Exploring a GitHub repository

馃摵 Video: Exploring a repository

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鈥檚 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.

Using issues

This is an issue 馃摉: 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.

Using GitHub Issues

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 馃摉
  • 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

馃摵 Video: Using issues


Managing notifications

Managing notifications

馃摵 Video: Watching, notifications, stars, and explore

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

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 repositories you鈥檙e watching link
  5. Select the Watching tab
  6. Click the Unwatch button to disable notifications, or Watch to enable them


Keep reading below to find your first task

@github-learning-lab

This comment has been minimized.

Copy link
Author

commented Jun 4, 2019

Step 1: Assign yourself

Unassigned issues don't have owners to look after them. When you鈥檙e assigned to an issue or pull request, it tells repository visitors and contributors that you'll be facilitating the conversation or task 馃挭.

鈱笍 Activity

  1. On the right side of the screen, under the "Assignees" section, click the gear icon and select yourself

For a printable version of the steps in this course, check out the Quick Reference Guide.


I'll respond when I detect you've assigned yourself to this issue.

Sometimes I respond too fast for the page to update! If you perform an expected action and don't see a response from me, wait a few seconds and refresh the page for your next steps.

@issue-label-bot

This comment has been minimized.

Copy link

commented Jun 4, 2019

Issue Label Bot is not confident enough to auto-label this issue. See dashboard for more details.

@dmitriz dmitriz self-assigned this Jun 4, 2019

@github-learning-lab

This comment has been minimized.

Copy link
Author

commented Jun 4, 2019

Step 2: Turn on GitHub Pages

馃帀 You're now the proud manager of this issue! Now that you've assigned yourself, people who drop by know that they're welcome to participate, but you'll be carrying this issue across the finish line. 馃槑.

Let's use GitHub Pages

Now, on to business! GitHub Pages allow you to serve a static site from a repository. We've filled this repository with some site content, but the rendered site isn't visible right now. Let's change that.

鈱笍 Activity: Enable GitHub Pages

  1. Click on the Settings tab in this repository
  2. Scroll down to the "GitHub Pages" section
  3. From the "Source" drop down, select master branch

Note: Even though you'll see an option to choose a theme, do not apply a theme at this point. We've protected the code so you can't make unintended changes. You'll have the opportunity to apply a theme when the course is completed.


I'll respond in this issue when I detect GitHub Pages has deployed your site.

Turning on GitHub Pages creates a deployment of your repository. I may take up to a minute to respond as I await the deployment.

@github-learning-lab

This comment has been minimized.

Copy link
Author

commented Jun 4, 2019

Step 3: Close an issue

You turned on GitHub Pages!

Your site is now visible to the public. Check it out at https://dmitriz.github.io/github-slideshow/.

Now that you鈥檝e completed the tasks in this issue, it's time to close it! Closing an issue tells other contributors that this particular conversation or task has come to an end.

鈱笍 Activity

  1. Click the Close issue button below

I'll respond when you've closed this issue.

@dmitriz dmitriz closed this Jun 4, 2019

@github-learning-lab

This comment has been minimized.

Copy link
Author

commented Jun 4, 2019

Consider this issue finished!


Head over to the next issue now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can鈥檛 perform that action at this time.