Finding and understanding example code

How can I learn from code on GitHub?

Learning from projects on GitHub is a great way of learning new techniques and finding inspiration for your own projects.

However, with millions of publicly available repositories on GitHub, finding code that applies to your project can be overwhelming. Even after you find the perfect repository, it can be difficult to navigate the codebase to find useful examples.

Instead of trying to understand an entire project, a better approach is to pick a single feature or function and see how it works. We can use Copilot Chat and GitHub's search functionality to locate a feature and follow it through the codebase. This is a great way to learn as we can see how the feature works all the way from the backend to the frontend.

In this guide, you'll learn how to do both by following an example scenario: learning how to load and display data from files on a Jekyll website. Then, you can apply the tips and techniques to other projects and programming languages.

Finding an example project

The first step is to find the right project to learn from.

Use Copilot Chat to identify a repository

The fastest way to find a project with code that you can learn from is to ask Copilot Chat to find repositories that match your criteria.

Open Copilot Chat and start a general purpose chat. Then ask:

Can you find some popular repositories that use Jekyll to display data from files in the repository?

Copilot will return links to relevant repositories, and you can ask follow-up questions about the repositories.

Often, Copilot will end its response with a link to GitHub search with more results. Next, we'll review these results.

Using search to identify more options

If Copilot included a link to search results, follow the link. If not, form your own search query by following the steps below.

1. Navigate to Advanced search.
2. In the "Advanced options" section, use the "Written in this language" dropdown to select a programming language. For our Jekyll site, we'll select "HTML".
3. Optionally, under "Repositories options", next to "With this many stars", type >150. This will help you find popular repositories that are likely well maintained.
4. Back at the top of the page, click Search.

Choosing a project

After reviewing the results from Copilot and search, we decide to use the github/choosealicense.com repository. This repository contains the source code for Choose a License, a Jekyll website that shares information about open source licenses.

We're particularly interested in the Licenses page, which displays popular open source licenses from data files.

Orienting yourself within the project

Before we dig into the code for displaying data files, let's orient ourselves in the repository in general.

It can be difficult to know where to start when you first visit a repository. While each project will organize itself in its own individual way, there are common documentation methods that we can usually rely upon to get our bearings.

The README.md file

It's always a good idea to read the README.md file, which is the front page of a repository and is automatically rendered beneath the list of files. Different maintainers will include different information, but you can often find information about the project, how to build it on your local machine, and links to documentation.

In the github/choosealicense.com repository, the README.md file explains where the license files live (/_licenses), the attributes each license can have, and how to get the website running on your computer.

Using Copilot Chat

If the README.md file doesn't give you all the answers, you can ask Copilot to help you navigate the repository and locate functionality.

To open Copilot Chat, click the GitHub Copilot icon next to the search bar and ask your question. For example:

What is the main landing page for this Jekyll website?

When you ask Copilot questions about a repository, it can return the relevant files, explain the part they play in the functionality, and include links.

The repository's wiki

Another possible source of information is the repository's wiki, a section of the repository specifically for hosting documentation. Every repository on GitHub comes equipped with the ability to use a wiki, but not every repository uses it. To access the wiki, click the Wiki tab in the repository.

Releases

If the repository's source code builds into an executable file, some repository maintainers will use the repository's releases to publish binary files. You can download and run these binary files to examine how the application works while exploring the codebase, without needing to build the project yourself.

You can find a repository's releases in the sidebar, to the right of the list of files and README.md.

Internal documentation

You can also look for internal documentation in the repository's contents. This could be a single Markdown file or a directory full of Markdown files. Common names to look for include "docs", "documentation", "wiki", "resources", "help", and "manual".

Navigating the source code

Now that we understand the overall structure of the repository, it's time to use GitHub search to find to the specific functionality we're looking for.

When you're in a repository and click into the search field at the top of the page, GitHub will automatically add the repo search qualifier so your search results are constrained to the repository you're viewing.

To get started, we need something to search for. This could be a string of text unique to the feature we're examining, or we could look at the HTML source of the page and find a particular class or id attribute.

In our example, we'll search for the text at the top of the licenses page, using this query: repo:github/choosealicense "If you’re looking for a reference table?". This returns one result, a file named licenses.html.

Now we can click on the result and dig deeper! licenses.html is the source of the "Licences" page we were looking for. We can see the string that we searched for and that each of the licenses is included with the code below:

{% include license-overview.html license-id="agpl-3.0" %}

Understanding the source code

Now that we've found the specific code we're interested in, we can move on to understanding it.

Asking Copilot Chat about the code

You can use Copilot to learn more about a file or even specific lines of code. Copilot will combine information about the programming language with the context from the repository to answer your questions in great detail.

Let's ask Copilot to explain what's happening on line 11, with the {% include %} tag. Click the line number. Then, to the right of the line, click . In the chat window, ask:

What's happening in this line?

Copilot will explain that the line is including the license-overview.html file and passing along "agpl-3.0" as the license-id to display.

Reading comments

Comments are human readable annotations that you can use to understand the code and are not executed. They are usually delimited with characters such as // or /*.

There are a few types of comments to look for:

• Line: Single-line comments that describe what a particular line is doing
• Block: Multi-line comments that might describe what an entire function or file is doing
• File: A block comment at the very beginning of a file, providing an overview of that particular part of the codebase

Looking up functions in programming language references

Every programming language will have a reference online, explaining every aspect of the language.

If you use a search engine to search for the programming language and the function, you should find a link to that function's reference page.

For our example, searching for jekyll include in a search engine should return the "Includes" documentation in the Jekyll documentation. If we read further into Jekyll's documentation, we can see that the licenses themselves are a collection in the _licenses directory.

To summarize what we've learned: the licenses.html file includes /_includes/license-overview.html for each license shown. The /_includes/license-overview.html file matches the license-id provided to a license in the /_licenses collection and renders the details.

Experimenting with small changes

If you're able to run the project locally on your computer, a great way to learn is to make little changes to see what happens.

You can start by changing text, then move on to making bigger changes, such as experimenting with how functions and files interact with each other.

Try finding the license-overview.html file in the _includes directory, then making changes to how the license is displayed or experimenting with how the license is loaded from the collection.

You could change the metadata at the beginning of one of the license files, change which attributes are displayed in license-overview.html, or even try adding your own attribute. When you've made your change, you can test it by following the README.md instructions to view it in your browser.

Applying what we've learnt

The github/choosealicense.com repository is a great example of a large Jekyll project and demonstrates just how much is possible with Jekyll and GitHub Pages. Can you apply what you've learnt from the structure of the repository, how it uses collections, and the way it includes the license data to build your own project?

Next steps

Now that you understand how the example code works, you may want to reuse it in your own project. Code reuse is a powerful part of software development, but there are important steps to follow to do it correctly and legally. For a full tutorial, see 프로젝트에서 다른 사용자의 코드 다시 사용.