chore: replace "master" with "main"

.github/ISSUE_TEMPLATE/1-documentation.yml

@@ -18,4 +18,4 @@ body:
   - type: textarea
     attributes:
       label: Are you interested in contributing a fix?
-      description: Indicate if this is something you would like to work on, and how we can best support you in doing so. More details [on contributing](https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc)
+      description: Indicate if this is something you would like to work on, and how we can best support you in doing so. More details [on contributing](https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc)

.github/ISSUE_TEMPLATE/2-wiki-migration.yml

@@ -24,4 +24,4 @@ body:
     id: info
     attributes:
       value: |
-        For contributors: [Wiki Migration Guidelines](https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#moving-documentation-from-jenkins-wiki)
+        For contributors: [Wiki Migration Guidelines](https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc#moving-documentation-from-jenkins-wiki)

.github/ISSUE_TEMPLATE/3-enhancement.yml

@@ -22,4 +22,4 @@ body:
   - type: textarea
     attributes:
       label: Are you interested in contributing to this improvement?
-      description: Indicate if this is something you would like to work on, and how we can best support you in doing so. More details [on contributing](https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc)
+      description: Indicate if this is something you would like to work on, and how we can best support you in doing so. More details [on contributing](https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc)

.github/ISSUE_TEMPLATE/4-bug.yml

@@ -34,4 +34,4 @@ body:
   - type: textarea
     attributes:
       label: Are you interested in contributing a fix?
-      description: Indicate if this is something you would like to work on, and how we can best support you in doing so. More details [on contributing](https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc)
+      description: Indicate if this is something you would like to work on, and how we can best support you in doing so. More details [on contributing](https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc)

.github/dependabot.yml

@@ -4,7 +4,7 @@ updates:
 
   # GitHub actions
   - package-ecosystem: "github-actions"
-    target-branch: master
+    target-branch: main
     directory: "/"
     schedule:
       # Check for updates to GitHub Actions every week

.github/workflows/compress-images.yaml

@@ -1,6 +1,6 @@
 # Image Actions will run in the following scenarios:
 # - on Pull Requests containing images (not including forks)
-# - on pushing of images to `master` (for forks)
+# - on pushing of images to `main` (for forks)
 # - on demand (https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/)
 # - at 11 PM every Sunday in anything gets missed with any of the above scenarios
 # For Pull Requests, the images are added to the PR.
@@ -15,7 +15,7 @@ on:
       - '**.webp'
   push:
     branches:
-      - master
+      - main
     paths:
       - '**.jpg'
       - '**.jpeg'

.github/workflows/updatecli.yaml

@@ -24,7 +24,7 @@ jobs:
           UPDATECLI_GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Run Updatecli in Apply mode
-        if: github.ref == 'refs/heads/master'
+        if: github.ref == 'refs/heads/main'
         run: updatecli apply --config ./updatecli/updatecli.d --values ./updatecli/values.github-action.yaml
         env:
           UPDATECLI_GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

CONTRIBUTING.adoc

@@ -12,10 +12,10 @@ toc::[]
 
 To contribute to this repository, follow these steps:
 
-1. link:https://guides.github.com/activities/forking/[Fork this repository] and ensure that you keep only the `master` branch.
-2. Create a new branch from your `master` branch and perform your work on this new branch, avoiding direct changes to the `master` branch.
+1. link:https://guides.github.com/activities/forking/[Fork this repository] and ensure that you keep only the `main` branch.
+2. Create a new branch from your `main` branch and perform your work on this new branch, avoiding direct changes to the `main` branch.
 3. Once your work is completed and committed to your branch, push the changes to your forked repository.
-4. link:https://help.github.com/articles/creating-a-pull-request-from-a-fork/[Create a pull request (PR)] from your branch to the `master` branch of this repository.
+4. link:https://help.github.com/articles/creating-a-pull-request-from-a-fork/[Create a pull request (PR)] from your branch to the `main` branch of this repository.
 
 Note that forking needs to be done only once. After forking, you can keep your fork up to date thanks to *Sync fork* or make further changes to your forked repository using the GitHub website file editor or by working on a local clone, as described below.
 
@@ -55,7 +55,7 @@ This group has various communication channels which can be used to discuss contr
 === Creating a fork
 
 Creating a fork, aka link:https://guides.github.com/activities/forking/[forking], makes a personal copy of another repository.
-Changes you make in your fork do not show up on the website until they are merged (via PR) to the `master` branch of the repository.
+Changes you make in your fork do not show up on the website until they are merged (via PR) to the `main` branch of the repository.
 If you are unfamiliar with how to create a fork or how forks work, refer to the link:https://guides.github.com/activities/forking/[GitHub tutorial on forking].
 
 === Using GitHub to edit files
@@ -425,9 +425,9 @@ For further examples of AsciiDoc source blocks, refer to the link:https://docs.a
 
 === Adding an event
 
-To add an event to the Jenkins event calendar, create a file in the `https://github.com/jenkins-infra/jenkins.io/tree/master/content/_data/events[content/_data/events/]` folder of this repo.
+To add an event to the Jenkins event calendar, create a file in the `https://github.com/jenkins-infra/jenkins.io/tree/main/content/_data/events[content/_data/events/]` folder of this repo.
 
-To create a file in this folder using the GitHub web editor, link:https://github.com/jenkins-infra/jenkins.io/new/master/content/_data/events[open this page in a new tab].
+To create a file in this folder using the GitHub web editor, link:https://github.com/jenkins-infra/jenkins.io/new/main/content/_data/events[open this page in a new tab].
 
 Name the file using the pattern `<DATE>-<CITY><OPTIONAL_ID>.adoc`:
 
@@ -593,7 +593,7 @@ Note that this file might be out of date or missing some entries, so common sens
 Notable special areas:
 
 * link:https://jenkins.io/project[Governance documents] - Managed by the link:https://www.jenkins.io/project/board/#current-board-members[Governance Board]
-* Jenkins core changelogs - Managed by the link:https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#roles[Jenkins core maintainers]
+* Jenkins core changelogs - Managed by the link:https://github.com/jenkinsci/jenkins/blob/main/docs/MAINTAINERS.adoc#roles[Jenkins core maintainers]
 * Security pages and advisories under `jenkins.io/security/` - Managed by the link:https://www.jenkins.io/security/team/[Jenkins Security Team]
 * Event pages under `jenkins.io/events/` - Managed by event organizers, link:https://www.jenkins.io/sigs/advocacy-and-outreach/[Advocacy and Outreach SIG] and the link:https://www.jenkins.io/project/team-leads/#events[Jenkins Events Officer]
 * SIG and sub-project pages - Managed by teams

Jenkinsfile

@@ -34,7 +34,7 @@ node('docker&&linux') {
         *
         *
         * git url: 'git://github.com/jenkinsci/jenkins.io',
-        *     branch: 'master'
+        *     branch: 'main'
         */
 
         /*

Jenkinsfile_k8s

@@ -11,7 +11,7 @@ pipeline {
   }
 
   triggers {
-    cron("${env.BRANCH_NAME == 'master' ? 'H/30 * * * *' : ''}")
+    cron("${env.BRANCH_NAME == 'main' ? 'H/30 * * * *' : ''}")
   }
 
   options {
@@ -46,7 +46,7 @@ pipeline {
 
     stage('Deploy to preview site') {
       when {
-        changeRequest target: 'master'
+        changeRequest target: 'main'
       }
       environment {
         NETLIFY_AUTH_TOKEN = credentials('netlify-auth-token')

README.adoc

@@ -12,6 +12,6 @@ useful and compelling web presence for the link:https://jenkins.io/[Jenkins auto
 == Contributing
 
 If you're interested in contributing to the site, please see our
-link:https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc[Contributing document]
+link:https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc[Contributing document]
 
-Documentation for Jenkins website maintenance is in the https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#maintainer-guide[maintainers guidelines].
+Documentation for Jenkins website maintenance is in the https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc#maintainer-guide[maintainers guidelines].

content/_layouts/frame.html.haml

@@ -112,7 +112,7 @@
 
     %jio-footer{:property => "https://www.jenkins.io",
       :githubRepo => "jenkins-infra/jenkins.io",
-      :githubBranch => "master",
+      :githubBranch => "main",
       :reportAProblemTemplate => "4-bug.yml",
       :sourcePath=> page.uneditable ? "" : "content#{page.relative_source_path}"}
 

content/artwork/index.html.haml

@@ -147,7 +147,7 @@ tight: true
       Adding a Logo
     %p
       In order to add a new logo, please refer to the 
-      %a{:href => 'https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#adding-a-logo'}
+      %a{:href => 'https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc#adding-a-logo'}
         CONTRIBUTING guidelines.
 
 = partial('anchors.html.haml', :selector => '.artwork-container');

content/blog/2017/08/2017-08-23-pull-requests-and-more.adoc

@@ -80,7 +80,7 @@ user documentation (link:/doc/[guided tour] and link:/doc/book/[handbook]) and
 developer documentation (link:/doc/developer/[tutorial], link:/doc/developer/guides/[how-to guides], and link:/doc/developer/book/[reference]).
 You can help the documentation by describing something important to you clearly and completely.
 
-Refer to the link:https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#adding-documentation[instructions for documentation contributors] to see how easy it is to help.
+Refer to the link:https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc#adding-documentation[instructions for documentation contributors] to see how easy it is to help.
 
 === Forty Five Minutes for Translation
 

content/blog/2017/10/2017-10-06-hacktoberfest.adoc

@@ -28,7 +28,7 @@ You can...
 
 * Write code
 * Improve documentation,
-write link:https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#adding-a-blog-post[blogposts]
+write link:https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc#adding-a-blog-post[blogposts]
 * Automate Tests
 * Translate and link:https://wiki.jenkins.io/display/JENKINS/Internationalization[internationalize] components
 * Design - artwork and UI improvements also count!
@@ -47,7 +47,7 @@ For example, you could contribute to the following components:
 * link:https://github.com/jenkinsci/jenkins[Jenkins Core]
 (link:https://github.com/jenkinsci/jenkins/blob/master/CONTRIBUTING.md[contributing])
 * link:https://github.com/jenkins-infra/jenkins.io/[Project Website]
-(link:https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc[contributing])
+(link:https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc[contributing])
 * Packaging (
 link:https://github.com/jenkinsci/docker[Docker],
 link:https://github.com/jenkinsci/packaging[native packages]

content/blog/2018/03/2018-03-12-browser-usage.adoc

@@ -137,4 +137,4 @@ Jenkins.io visitors are a majority of desktop users.
 They are aligned with the world trends when we talk about desktop browsers however only a minority of them come from a mobile.
 This is probably because jenkins.io is not (yet) mobile friendly and obsiously this would be a nice improvement to have.
 
-All https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc[contributions] are welcomed and especially for mobile user experience.
+All https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc[contributions] are welcomed and especially for mobile user experience.

content/blog/2018/10/2018-10-01-hacktoberfest.adoc

@@ -37,7 +37,7 @@ You can...
    mostly Java, Groovy, and JavaScript + Go in Jenkins
 ** You can also find components in Ruby/Kotlin, and even native components in C/C++
 * **Document** - Improve documentation
-* **Blog** - write link:https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#adding-a-blog-post[blogposts] about Jenkins
+* **Blog** - write link:https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc#adding-a-blog-post[blogposts] about Jenkins
 * **Localize** -  link:https://wiki.jenkins.io/display/JENKINS/Internationalization[Localize] Jenkins components
 * **Design** - link:/artwork[artwork] and UI improvements also count!
 * **Organize** - Organize a local meetup for Jenkins & Hacktoberfest (see below)
@@ -66,7 +66,7 @@ Here is a list of Jenkins subprojects with maintainers who have committed to del
 | link:/[Jenkins Website]
 | Extend and improve Jenkins documentation, add your own blogpost.
 
-  link:https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc[Contributing guidelines]
+  link:https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc[Contributing guidelines]
 
 | link:https://jenkins-x.io/[Jenkins X]
 | Try out the project and create new demos,

content/blog/2019/03/2019-03-29-becoming-contributor-intro.adoc

@@ -84,7 +84,7 @@ ahead with it.
 === The website repository
 
 In the ”Document” section there is a link to the
-https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc[contributing guidelines of the jenkins.io repository].
+https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc[contributing guidelines of the jenkins.io repository].
 The CONTRIBUTING file is a common file present in the root folder of most open-source-project repositories.
 
 Following the link to that file, I reached the jenkins.io repository, which is the one that contains the sources for
@@ -139,7 +139,7 @@ image::/images/post-images/2019-03-29-becoming-contributor/creating-pr.png[]
 
 When a PR to this repository is created, we notice there are some checks that start running. Jenkins repositories are
 configured to notify the https://ci.jenkins.io/[“Jenkins on Jenkins”], which runs the corresponding CI pipelines for
-each repository, as described in the corresponding https://github.com/jenkins-infra/jenkins.io/blob/master/Jenkinsfile[Jenkinsfile].
+each repository, as described in the corresponding https://github.com/jenkins-infra/jenkins.io/blob/main/Jenkinsfile[Jenkinsfile].
 
 Once the checks are completed, we can see the result in the PR:
 

content/blog/2019/05/2019-05-11-docs-sig-announcement.adoc

@@ -26,7 +26,7 @@ The Jenkins Documentation SIG would love to have your help with:
 
 == How can I fix a documentation bug?
 
-Instructions for contributing to the Jenkins documentation are in the link:https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#getting-started[CONTRIBUTING file] of the site repository.
+Instructions for contributing to the Jenkins documentation are in the link:https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc#getting-started[CONTRIBUTING file] of the site repository.
 Follow the instructions in that file and submit pull requests for review.
 
 Instructions for contributing to the Jenkins X documentation are on the link:https://jenkins-x.io/community/documentation/[Jenkins X documentation site].

content/blog/2019/10/2019-10-21-plugin-docs-on-github.adoc

@@ -94,7 +94,7 @@ and you are welcome to submit pull requests against any repository.
 Migrating documentation:
 
 * link:/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github[Migrating plugin documentation from Wiki to GitHub]
-* link:https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#moving-documentation-from-jenkins-wiki[Moving documentation from Jenkins Wiki to jenkins.io]
+* link:https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc#moving-documentation-from-jenkins-wiki[Moving documentation from Jenkins Wiki to jenkins.io]
 * jira:JENKINS-59467[Template issue for plugin docs migration]
 * link:https://issues.jenkins.io/issues/?filter=18650&jql=project%20%3D%20WEBSITE%20AND%20labels%20%3D%20newbie-friendly%20and%20status%20in%20(Open%2C%20Reopened%2C%20%22To%20Do%22)[Newbie-friendly documentation tasks]
 

content/blog/2019/12/2019-12-20-call-for-mentors.adoc

@@ -36,7 +36,7 @@ So send us your project ideas before the beginning of February so they can get a
 
 For 2020, we have simplified the process.
 Simply create a pull-request with your idea in a `.adoc` file 
-in the link:https://github.com/jenkins-infra/jenkins.io/tree/master/content/projects/gsoc/2020/project-ideas[idea folder].
+in the link:https://github.com/jenkins-infra/jenkins.io/tree/main/content/projects/gsoc/2020/project-ideas[idea folder].
 It is no longer necessary to submit a Google Doc, but it will still work if you want to do that.
 See the link:/projects/gsoc/proposing-project-ideas[instructions] on submitting ideas which include an `.adoc` template and some examples.
 

content/blog/2020/06/2020-06-08-hackfest-docs-results.adoc

@@ -105,7 +105,7 @@ image:/images/post-images/2020-06-08-docs-from-hackfest/plugins-site.png[Plugins
 
 There is still much to do in Jenkins documentation and we need your help to do it.
 There are many ways to link:/participate/[participate] in the Jenkins project, including link:/participate/document[documentation].
-See the link:https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc[contributing guidelines] for detailed instructions.
+See the link:https://github.com/jenkins-infra/jenkins.io/blob/main/CONTRIBUTING.adoc[contributing guidelines] for detailed instructions.
 Join the https://app.gitter.im/#/room/#jenkins/docs:matrix.org[documentation chat] for personalized help and encouragement.
 
 The Jenkins project has been also accepted to link:https://developers.google.com/season-of-docs[Google Season of Docs] this year.

content/blog/2020/12/2020-12-16-call-for-mentors.adoc

@@ -36,7 +36,7 @@ Please send us your project ideas before the beginning of February so they can g
 === How to submit a project idea
 
 Create a pull-request with your idea in a `.adoc` file 
-in the link:https://github.com/jenkins-infra/jenkins.io/tree/master/content/projects/gsoc/2021/project-ideas[project ideas].
+in the link:https://github.com/jenkins-infra/jenkins.io/tree/main/content/projects/gsoc/2021/project-ideas[project ideas].
 It is not necessary to submit a Google Doc, but it will still work if you want to do that.
 See the link:/projects/gsoc/proposing-project-ideas[instructions] on submitting ideas which include an `.adoc` template and some examples.
 

content/blog/2022/01/2022-01-07-gsoc-2022.adoc

@@ -34,7 +34,7 @@ Anyone can submit a project idea, but of course we like it even better if you me
 Please send us your project ideas before the beginning of February so they can get a proper review by the GSoC committee and by the community.
 
 === How to submit a project idea
-Create a pull-request with your idea in a .adoc file in the link:https://github.com/jenkins-infra/jenkins.io/tree/master/content/projects/gsoc/2022/project-ideas[project ideas].
+Create a pull-request with your idea in a .adoc file in the link:https://github.com/jenkins-infra/jenkins.io/tree/main/content/projects/gsoc/2022/project-ideas[project ideas].
 It is not necessary to submit a Google Doc, but it will still work if you want to do that.
 See the link:/projects/gsoc/proposing-project-ideas/[instructions] on submitting ideas which include an .adoc template and some examples.
 

content/blog/2022/11/2022-11-16-gsoc-2023.adoc

@@ -36,7 +36,7 @@ Anyone can submit a project idea, but of course we like it even better if you me
 Please send us your project ideas before the beginning of February so they can get a proper review by the GSoC committee and by the community.
 
 === How to submit a project idea
-Create a pull-request with your idea in a .adoc file in the link:https://github.com/jenkins-infra/jenkins.io/tree/master/content/projects/gsoc/2023/project-ideas[project ideas]. 
+Create a pull-request with your idea in a .adoc file in the link:https://github.com/jenkins-infra/jenkins.io/tree/main/content/projects/gsoc/2023/project-ideas[project ideas]. 
 It is not necessary to submit a Google Doc, but it will still work if you want to do that.
 See the link:/projects/gsoc/proposing-project-ideas/[instructions] on submitting ideas which include an .adoc template and some examples.