Welcome

## :tada: Welcome to Securing your workflows!

In this course, you'll learn how to build and host a secure repository in GitHub. A secure repository is important for many reasons.
- Prevents exposing sensitive data
- Enforces secure development best practices
- Guards against unintended access rights permissions

In this course you will learn how to:

- Opt-in to vulnerability alerts for private repositories
- _Note: These security settings are default for public repositories that are not forks._
- Detect and fix vulnerable dependencies when notified by a vulnerability alert
- Follow security best practices to protect sensitive data by using a `.gitignore` file

### New to GitHub?

For this course, you'll need to be comfortable with the GitHub Flow. If you need a refresher on the GitHub flow, check out the [the Introduction to GitHub course](https://lab.github.com/courses/introduction-to-github).

## Step 1: Your project on GitHub Pages

This project is centered around a memory game that will be deployed with GitHub Pages.

### :keyboard: Activity: Enable GitHub Pages

1. Click the [**Settings**](https://github.com/Ayushparikh-code/security-on-github/settings) tab in your repository.
1. Scroll down to **GitHub Pages** and select `main` as a **Source**.

For a printable version of the steps in this course, check out the [Quick Reference Guide](https://lab.github.com/public/securing-your-workflows.pdf).

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

Return to this issue for my next comment.

> _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. Then refresh the page for your next steps._

Start with the issue body and review the GitHub Pages activity, including the linked repository Settings page and the Quick Reference Guide. Done would mean confirming that the course instructions for selecting main as the GitHub Pages source are accurate; no source files or tests are named.

Written by the indexing model from the issue text.