fluxcd
/
source-controller
mirror of https://github.com/fluxcd/source-controller.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Set default branch to main 

Signed-off-by: stefanprodan <stefan.prodan@gmail.com>
This commit is contained in:
stefanprodan 2020-10-05 15:09:46 +03:00
parent 2331334bd0
commit f81b479382
6 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/workflows/e2e.yaml vendored
View File

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

4
.github/workflows/fossa.yaml vendored
View File

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

2
.github/workflows/release.yml vendored
View File

@ -102,7 +102,7 @@ jobs:
draft: false draft: false
prerelease: true prerelease: true
body: | 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 - name: Upload artifacts
if: github.event_name == 'push' && contains(github.ref, 'refs/tags/') if: github.event_name == 'push' && contains(github.ref, 'refs/tags/')
id: upload-release-asset id: upload-release-asset

4
CHANGELOG.md
View File

@ -24,7 +24,7 @@ The Helm package was updated to v3.3.4.
## 0.0.17 (2020-09-18) ## 0.0.17 (2020-09-18)
This prerelease comes with support for S3 compatible storage sources 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. The Helm package was updated to v3.3.2.
## 0.0.16 (2020-09-12) ## 0.0.16 (2020-09-12)
@ -122,7 +122,7 @@ to be specified on `GitRepository` objects.
This prerelease comes with Kubernetes events dispatching. This prerelease comes with Kubernetes events dispatching.
The reconciliation events can be forwarded to notification controller The reconciliation events can be forwarded to notification controller
and alerting can be configured for Slack, MS Teams, Discord and Rocket chat 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) ## 0.0.1 (2020-06-24)

2
README.md
View File

@ -2,7 +2,7 @@
[![e2e](https://github.com/fluxcd/source-controller/workflows/e2e/badge.svg)](https://github.com/fluxcd/kustomize-controller/actions) [![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) [![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) [![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 The source-controller is a Kubernetes operator, specialised in artifacts acquisition

7
docs/internal/release.md
View File

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