Rename master branch to main

Signed-off-by: Bernd Verst <github@bernd.dev>
This commit is contained in:
Bernd Verst 2023-11-06 11:43:03 -08:00
parent f4e73b0e65
commit 88eb49c838
8 changed files with 16 additions and 16 deletions

View File

@ -24,7 +24,7 @@ on:
- 'release-*'
pull_request:
branches:
- 'master'
- 'main'
- 'release-*'
jobs:

View File

@ -17,12 +17,12 @@ on:
push:
branches:
- feature/*
- gh-readonly-queue/master/*
- gh-readonly-queue/main/*
pull_request:
branches:
- master
- main
- feature/*
- gh-readonly-queue/master/*
- gh-readonly-queue/main/*
merge_group:
jobs:

View File

@ -22,12 +22,12 @@ on:
push:
branches:
- 'release-*'
- 'gh-readonly-queue/master/*'
- 'gh-readonly-queue/main/*'
pull_request:
branches:
- 'master'
- 'main'
- 'release-*'
- 'gh-readonly-queue/master/*'
- 'gh-readonly-queue/main/*'
merge_group:
jobs:
@ -352,7 +352,7 @@ jobs:
# Upload logs for test analytics to consume
- name: Upload test results
if: always()
uses: actions/upload-artifact@master
uses: actions/upload-artifact@main
with:
name: ${{ matrix.component }}_conformance_test
path: ${{ env.TEST_OUTPUT_FILE_PREFIX }}_conformance.*

View File

@ -51,7 +51,7 @@ jobs:
with:
workflow: certification.yml
workflow_conclusion: "success"
branch: master
branch: main
event: schedule
if_no_artifact_found: error
name: cert_code_cov
@ -62,7 +62,7 @@ jobs:
with:
workflow: conformance.yml
workflow_conclusion: "success"
branch: master
branch: main
event: schedule
if_no_artifact_found: error
name: conf_code_cov

View File

@ -15,13 +15,13 @@ name: fossa
on:
push:
branches:
- master
- main
- release-*
tags:
- v*
pull_request:
branches:
- master
- main
- release-*
workflow_dispatch: {}
jobs:

View File

@ -224,7 +224,7 @@ check-component-metadata:
$(RUN_BUILD_TOOLS) generate-metadata-analyzer-app --outputfile ./metadataanalyzer/main.go
cd metadataanalyzer && \
go mod init metadataanalyzer && \
go get "github.com/dapr/components-contrib@master" && \
go get "github.com/dapr/components-contrib@main" && \
go mod edit -replace "github.com/dapr/components-contrib"="../" && \
go mod tidy && \
go build -tags metadata . && \

View File

@ -1,8 +1,8 @@
# Components Contrib
[![Build, Lint, Unit Test - complete matrix](https://github.com/dapr/components-contrib/actions/workflows/components-contrib-all.yml/badge.svg?branch=master&event=schedule)](https://github.com/dapr/components-contrib/actions/workflows/components-contrib-all.yml)
[![Build, Lint, Unit Test - complete matrix](https://github.com/dapr/components-contrib/actions/workflows/components-contrib-all.yml/badge.svg?branch=main&event=schedule)](https://github.com/dapr/components-contrib/actions/workflows/components-contrib-all.yml)
[![Discord](https://img.shields.io/discord/778680217417809931)](https://discord.com/channels/778680217417809931/781589820128493598)
[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/dapr/components-contrib/blob/master/LICENSE)
[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/dapr/components-contrib/blob/main/LICENSE)
[![FOSSA Status](https://app.fossa.com/api/projects/custom%2B162%2Fgithub.com%2Fdapr%2Fcomponents-contrib.svg?type=shield)](https://app.fossa.com/projects/custom%2B162%2Fgithub.com%2Fdapr%2Fcomponents-contrib?ref=badge_shield)
The purpose of Components Contrib is to provide open, community-driven, reusable components for building distributed applications.

View File

@ -18,7 +18,7 @@
1. All components/services tested in the automated tests are currently manually setup by the Dapr team and run in an environment maintained by the Dapr team. As a contributor, follow the next two steps for integrating a new component with conformance tests.
2. If the component is tested locally within a docker container requiring no secrets, then add the component to the `pr-components` step in conformance test workflow `.github/conformance.yml`. `pr-components` step generates the component matrix for which the conformance tests will be run on each PR.
3. If the component is tested against a service and requires secrets, then add the component to the `cron-components` step in conformance test workflow `.github/conformance.yml`. `cron-components` defines the components for which the conformance test will be run against the master code in a scheduled manner.
3. If the component is tested against a service and requires secrets, then add the component to the `cron-components` step in conformance test workflow `.github/conformance.yml`. `cron-components` defines the components for which the conformance test will be run against the main code in a scheduled manner.
## Integrating a new component with conformance tests