Merge pull request #163 from fluxcd/main-branch

Set default branch to main

Author: stefanprodan

.github/workflows/e2e.yaml

@@ -4,7 +4,7 @@ on:
   pull_request:
   push:
     branches:
-      - master
+      - main
 
 jobs:
   kind:

.github/workflows/fossa.yaml

@@ -1,9 +1,9 @@
 name: FOSSA
 on:
   push:
-    branches: [master]
+    branches: [main]
   pull_request:
-    branches: [master]
+    branches: [main]
 
 jobs:
   build:

.github/workflows/release.yml

@@ -102,7 +102,7 @@ jobs:
           draft: false
           prerelease: true
           body: |
-            [CHANGELOG](https://github.com/fluxcd/source-controller/blob/master/CHANGELOG.md)
+            [CHANGELOG](https://github.com/fluxcd/source-controller/blob/main/CHANGELOG.md)
       - name: Upload artifacts
         if: github.event_name == 'push' && contains(github.ref, 'refs/tags/')
         id: upload-release-asset

CHANGELOG.md

@@ -24,7 +24,7 @@ The Helm package was updated to v3.3.4.
 ## 0.0.17 (2020-09-18)
 
 This prerelease comes with support for S3 compatible storage sources
-defined as [buckets](https://github.com/fluxcd/source-controller/blob/master/docs/spec/v1alpha1/buckets.md).
+defined as [buckets](https://github.com/fluxcd/source-controller/blob/main/docs/spec/v1alpha1/buckets.md).
 The Helm package was updated to v3.3.2.
 
 ## 0.0.16 (2020-09-12)
@@ -122,7 +122,7 @@ to be specified on `GitRepository` objects.
 This prerelease comes with Kubernetes events dispatching.
 The reconciliation events can be forwarded to notification controller
 and alerting can be configured for Slack, MS Teams, Discord and Rocket chat
-using the [notification.fluxcd.io API](https://github.com/fluxcd/notification-controller/tree/master/docs/spec).
+using the [notification.fluxcd.io API](https://github.com/fluxcd/notification-controller/tree/main/docs/spec).
 
 ## 0.0.1 (2020-06-24)
 

README.md

@@ -2,7 +2,7 @@
 
 [![e2e](https://github.com/fluxcd/source-controller/workflows/e2e/badge.svg)](https://github.com/fluxcd/kustomize-controller/actions)
 [![report](https://goreportcard.com/badge/github.com/fluxcd/source-controller)](https://goreportcard.com/report/github.com/fluxcd/source-controller)
-[![license](https://img.shields.io/github/license/fluxcd/source-controller.svg)](https://github.com/fluxcd/source-controller/blob/master/LICENSE)
+[![license](https://img.shields.io/github/license/fluxcd/source-controller.svg)](https://github.com/fluxcd/source-controller/blob/main/LICENSE)
 [![release](https://img.shields.io/github/release/fluxcd/source-controller/all.svg)](https://github.com/fluxcd/source-controller/releases)
 
 The source-controller is a Kubernetes operator, specialised in artifacts acquisition

docs/internal/release.md

@@ -2,12 +2,13 @@
 
 To release a new version the following steps should be followed:
 
-1. Create a new branch from `master` i.e. `release-<next semver>`. This
+1. Create a `api/<next semver>` tag and push it to remote.
+1. Create a new branch from `main` i.e. `release-<next semver>`. This
    will function as your release preparation branch.
 1. Add an entry to the `CHANGELOG.md` for the new release and change the
    `newTag` value in ` config/manager/kustomization.yaml` to that of the
    semver release you are going to make. Commit and push your changes.
-1. Create a PR for your release branch and get it merged into `master`.
-1. Create a `<next semver>` tag for the merge commit in `master` and
+1. Create a PR for your release branch and get it merged into `main`.
+1. Create a `<next semver>` tag for the merge commit in `main` and
    push it to remote.
 1. Confirm CI builds and releases the newly tagged version.