From 427f2389d6b8a49a9439cd6e2248b4f3274f37a2 Mon Sep 17 00:00:00 2001
From: Briana Swift <brianamarie@github.com>
Date: Mon, 30 Nov 2020 11:10:01 +0100
Subject: [PATCH] Rename master to main

---
 README.md                                   | 4 ++--
 config.yml                                  | 2 +-
 responses/00_class-introduction-issue.md    | 4 ++--
 responses/01_update-index.md                | 2 +-
 responses/03_change-theme.md                | 2 +-
 responses/es/00_class-introduction-issue.md | 4 ++--
 responses/es/01_update-index.md             | 2 +-
 responses/es/03_change-theme.md             | 2 +-
 8 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md
index 73248b6..811e482 100644
--- a/README.md
+++ b/README.md
@@ -14,9 +14,9 @@ For more information on the goals of this course, check out the [`course-details
 
 ## Contribute
 
-See something we could improve? Check out the contributing guide in the [community contributors repository](https://github.com/githubtraining/community-contributors/blob/master/CONTRIBUTING.md) for more information on the types of contributions we :heart: and instructions.
+See something we could improve? Check out the contributing guide in the [community contributors repository](https://github.com/githubtraining/community-contributors/blob/main/CONTRIBUTING.md) for more information on the types of contributions we :heart: and instructions.
 
-We :heart: our community and take great care to ensure it is fun, safe and rewarding. Please review our [Code of Conduct](https://github.com/githubtraining/community-contributors/blob/master/CODE_OF_CONDUCT.md) for community expectations and guidelines for reporting concerns.
+We :heart: our community and take great care to ensure it is fun, safe and rewarding. Please review our [Code of Conduct](https://github.com/githubtraining/community-contributors/blob/main/CODE_OF_CONDUCT.md) for community expectations and guidelines for reporting concerns.
 
 ## License
 
diff --git a/config.yml b/config.yml
index d01e2ea..2259b05 100644
--- a/config.yml
+++ b/config.yml
@@ -85,7 +85,7 @@ steps:
       - type: gate
         left: '%payload.pull_request.base.ref%'
         operator: ===
-        right: master
+        right: main
       - type: updateBranchProtection
       - type: octokit
         method: repos.getPages
diff --git a/responses/00_class-introduction-issue.md b/responses/00_class-introduction-issue.md
index e09fbeb..10bfed4 100644
--- a/responses/00_class-introduction-issue.md
+++ b/responses/00_class-introduction-issue.md
@@ -16,10 +16,10 @@ For this course, you'll need to know how to create a branch on GitHub, commit ch
 
 ### :keyboard: Activity: Generate a GitHub Pages site
 
-The first step to publishing your blog to the web is to enable GitHub Pages on this repository <sup>[:book:](https://help.github.com/articles/github-glossary/#repository)</sup>. When you enable GitHub Pages on a repository, GitHub takes the content that's on the master branch and publishes a website based on its contents.
+The first step to publishing your blog to the web is to enable GitHub Pages on this repository <sup>[:book:](https://help.github.com/articles/github-glossary/#repository)</sup>. When you enable GitHub Pages on a repository, GitHub takes the content that's on the main branch and publishes a website based on its contents.
 
 1. Under your repository name, click [**Settings**]({{ repoUrl }}/settings).
-1. In the "GitHub Pages" section, in the Source drop-down, select **master branch**.
+1. In the "GitHub Pages" section, in the Source drop-down, select **main branch**.
 
 After GitHub Pages is enabled and the site is started, we'll be ready to create some more content. 
 
diff --git a/responses/01_update-index.md b/responses/01_update-index.md
index 25dae35..bd29764 100644
--- a/responses/01_update-index.md
+++ b/responses/01_update-index.md
@@ -8,7 +8,7 @@ Your repository has an `index.md` file so we can update it to include your perso
 
 ### :keyboard: Activity: Create your homepage
 
-1. Navigate to the **Code** tab of this repository, and browse to the `index.md` file, or click this link [here]({{ repoUrl }}/blob/master/index.md)
+1. Navigate to the **Code** tab of this repository, and browse to the `index.md` file, or click this link [here]({{ repoUrl }}/blob/main/index.md)
 2. In the upper right corner, click the ![octicon-pencil] icon to edit the `index.md` file
 3. Type the content you want on your homepage
 4. Scroll to the bottom, type a commit message, and click **Create a new branch for this commit and start a pull request**
diff --git a/responses/03_change-theme.md b/responses/03_change-theme.md
index 2f71a60..0282e1d 100644
--- a/responses/03_change-theme.md
+++ b/responses/03_change-theme.md
@@ -12,7 +12,7 @@ You can check out the `_config.yml` file on the **Code** tab of your repository.
 
 Let's change the `_config.yml` so it's a perfect fit for your new blog. First, we need to use a blog-ready theme. For this activity, we will use a theme named `minima`.
 
-1. Navigate to the **Code** tab of this repository, and browse to the `_config.yml` file, or click this link [here]({{ repoUrl }}/blob/master/_config.yml).
+1. Navigate to the **Code** tab of this repository, and browse to the `_config.yml` file, or click this link [here]({{ repoUrl }}/blob/main/_config.yml).
 2. In the upper right corner, click :pencil2: to open the file editor.
 3. Add a `theme:` set to **minima** so it shows in the `_config.yml` file as below:
     ```
diff --git a/responses/es/00_class-introduction-issue.md b/responses/es/00_class-introduction-issue.md
index dc1b5ab..dbaab50 100644
--- a/responses/es/00_class-introduction-issue.md
+++ b/responses/es/00_class-introduction-issue.md
@@ -16,10 +16,10 @@ Para este curso necesitas saber cómo crear una rama (_branch_) en GitHub, confi
 
 ### :keyboard: Actividad: Genera un sitio web con GitHub Pages
 
-El primer paso para publicar tu blog en la web es activar GitHub Pages en este repositorio <sup>[:book:](https://help.github.com/articles/github-glossary/#repository)</sup>. Cuando habilitas GitHub Pages para un repositorio, GitHub toma el contenido que tenga en el branc `master` y publica un sitio web basado en esos contenidos.
+El primer paso para publicar tu blog en la web es activar GitHub Pages en este repositorio <sup>[:book:](https://help.github.com/articles/github-glossary/#repository)</sup>. Cuando habilitas GitHub Pages para un repositorio, GitHub toma el contenido que tenga en el branc `main` y publica un sitio web basado en esos contenidos.
 
 1. Debajo del nombre de tu repositorio, haz clic en [**Settings**]({{ repoUrl }}/settings) (Ajustes).
-1. En la sección "GitHub Pages", en el desplegable Source, selecciona **master branch**.
+1. En la sección "GitHub Pages", en el desplegable Source, selecciona **main branch**.
 
 Una vez que GitHub Pages se ha activado y se ha iniciado el sitio web, estaremos listos para crear algún contenido más. 
 
diff --git a/responses/es/01_update-index.md b/responses/es/01_update-index.md
index 44db1f5..03d961b 100644
--- a/responses/es/01_update-index.md
+++ b/responses/es/01_update-index.md
@@ -8,7 +8,7 @@ Tu repositorio tiene un archivo `index.md`, así que podemos actualizarlo para q
 
 ### :keyboard: Actividad: Crea tu página inicial
 
-1. Navega a la pestaña **Code** de este repositorio y accede al archivo `index.md`, o haz clic en [este enlace]({{ repoUrl }}/blob/master/index.md)
+1. Navega a la pestaña **Code** de este repositorio y accede al archivo `index.md`, o haz clic en [este enlace]({{ repoUrl }}/blob/main/index.md)
 2. En la esquina superior derecha, haz clic en el icono a la derecha del archivo para editar el archivo `index.md` 
 3. Escribe el contenido que quieres que aparezca en tu página principal
 4. Haz scroll hasta la parte inferior, escribe un mensaje de commit y haz clic en **Create a new branch for this commit and start a pull request**
diff --git a/responses/es/03_change-theme.md b/responses/es/03_change-theme.md
index fe82df0..40f78cb 100644
--- a/responses/es/03_change-theme.md
+++ b/responses/es/03_change-theme.md
@@ -14,7 +14,7 @@ Vamos a modificar `_config.yml` para que refleje perfectamente con tu nuevo blog
 
 
 
-1. Navega a la pestaña **Code** de este repositorio y hasta el archivo `_config.yml`, o haz clic en [este enlace]({{ repoUrl }}/blob/master/_config.yml).
+1. Navega a la pestaña **Code** de este repositorio y hasta el archivo `_config.yml`, o haz clic en [este enlace]({{ repoUrl }}/blob/main/_config.yml).
 2. En la esquina superior derecha, haz clic en :pencil2: para abrir el editor.
 3. Añade un `theme:` que especifique **minima**, de forma que se vea así en tu archivo `_config.yml`:
     ```

<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
<html xmlns='http://www.w3.org/1999/xhtml'>
<head>
<title>pFad - Phonifier reborn</title>
<meta http-equiv='Content-Type' content='text/html; charset=utf-8' />
</head>
<body>
<h1>Pfad - The Proxy pFad of &#169; 2024 Garber Painting. All rights reserved.</h1>


<!-- Disclaimer -->
<p>Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.</p>
<br>
<p>Alternative Proxies:</p><p><a href="http://rainy.clevelandohioweatherforecast.com/php-proxy/index.php?q=https://github.com/githubtraining/github-pages/compare/v13.4.0...v14.0.0.patch" target="_blank">Alternative Proxy</a></p><p><a href="http://rainy.clevelandohioweatherforecast.com/pFad/index.php?u=https://github.com/githubtraining/github-pages/compare/v13.4.0...v14.0.0.patch" target="_blank">pFad Proxy</a></p><p><a href="http://rainy.clevelandohioweatherforecast.com/pFad/v3index.php?u=https://github.com/githubtraining/github-pages/compare/v13.4.0...v14.0.0.patch" target="_blank">pFad v3 Proxy</a></p><p><a href="http://rainy.clevelandohioweatherforecast.com/pFad/v4index.php?u=https://github.com/githubtraining/github-pages/compare/v13.4.0...v14.0.0.patch" target="_blank">pFad v4 Proxy</a></p></body>
</html>