8000 ci: rename master branch to main (#263) · jrmfg/functions-framework-python@8829aed · GitHub
[go: up one dir, main page]
Skip to content

Commit 8829aed

Browse files
HKWinterhalterHKWinterhalter
authored
ci: rename master branch to main (GoogleCloudPlatform#263)
* ci: rename master branch to main * ci: retarget buildpack integration tests to latest * retarget buildpack integration tests to conformance main
1 parent 3bed433 commit 8829aed

File tree

9 files changed

+16
-16
lines changed

9 files changed

+16
-16
lines changed

‎.github/workflows/buildpack-integration-test.yml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ name: Buildpack Integration Test
33
on:
44
push:
55
branches:
6-
- master
6+
- main
77
pull_request:
88
workflow_dispatch:
99
# Runs every day on 12:00 AM PST
@@ -15,7 +15,7 @@ permissions: read-all
1515

1616
jobs:
1717
python37:
18-
uses: GoogleCloudPlatform/functions-framework-conformance/.github/workflows/buildpack-integration-test.yml@v1.8.4
18+
uses: GoogleCloudPlatform/functions-framework-conformance/.github/workflows/buildpack-integration-test.yml@main
1919
with:
2020
http-builder-source: 'tests/conformance'
2121
http-builder-target: 'write_http_declarative'
@@ -26,7 +26,7 @@ jobs:
2626
builder-runtime-version: '3.7'
2727
start-delay: 5
2828
python38:
29-
uses: GoogleCloudPlatform/functions-framework-conformance/.github/workflows/buildpack-integration-test.yml@v1.8.4
29+
uses: GoogleCloudPlatform/functions-framework-conformance/.github/workflows/buildpack-integration-test.yml@main
3030
with:
3131
http-builder-source: 'tests/conformance'
3232
http-builder-target: 'write_http_declarative'
@@ -37,7 +37,7 @@ jobs:
3737
builder-runtime-version: '3.8'
3838
start-delay: 5
3939
python39:
40-
uses: GoogleCloudPlatform/functions-framework-conformance/.github/workflows/buildpack-integration-test.yml@v1.8.4
40+
uses: GoogleCloudPlatform/functions-framework-conformance/.github/workflows/buildpack-integration-test.yml@main
4141
with:
4242
http-builder-source: 'tests/conformance'
4343
http-builder-target: 'write_http_declarative'
@@ -48,7 +48,7 @@ jobs:
4848
builder-runtime-version: '3.9'
4949
start-delay: 5
5050
python310:
51-
uses: GoogleCloudPlatform/functions-framework-conformance/.github/workflows/buildpack-integration-test.yml@v1.8.4
51+
uses: GoogleCloudPlatform/functions-framework-conformance/.github/workflows/buildpack-integration-test.yml@main
5252
with:
5353
http-builder-source: 'tests/conformance'
5454
http-builder-target: 'write_http_declarative'
@@ -57,4 +57,4 @@ jobs:
5757
prerun: 'tests/conformance/prerun.sh ${{ github.sha }}'
5858
builder-runtime: 'python310'
5959
builder-runtime-version: '3.10'
60-
start-delay: 5
60+
start-delay: 5

‎.github/workflows/codeql.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,10 @@ name: "CodeQL"
1313

1414
on:
1515
push:
16-
branches: ["master"]
16+
branches: ["main"]
1717
pull_request:
1818
# The branches below must be a subset of the branches above
19-
branches: ["master"]
19+
branches: ["main"]
2020
schedule:
2121
- cron: "0 0 * * 1"
2222

‎.github/workflows/conformance.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ name: Python Conformance CI
22
on:
33
push:
44
branches:
5-
- 'master'
5+
- 'main'
66
pull_request:
77

88
# Declare default permissions as read only.

‎.github/workflows/lint.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ name: Python Lint CI
22
on:
33
push:
44
branches:
5-
- master
5+
- main
66
pull_request:
77
permissions:
88
contents: read

‎.github/workflows/release.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ jobs:
2828
- name: Build distributions
2929
run: python -m build
3030
- name: Publish
31-
uses: pypa/gh-action-pypi-publish@54d67ed3c50a769c633f7db8063c9e634709c1b0 # master
31+
uses: pypa/gh-action-pypi-publish@54d67ed3c50a769c633f7db8063c9e634709c1b0 # main
3232
with:
3333
user: __token__
3434
password: ${{ secrets.PYPI_API_TOKEN }}

‎.github/workflows/scorecard.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ on:
88
schedule:
99
- cron: '0 */12 * * *'
1010
push:
11-
branches: [ "master" ]
11+
branches: [ "main" ]
1212
workflow_dispatch:
1313

1414
# Declare default permissions as read only.

‎.github/workflows/unit.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ name: Python Unit CI
22
on:
33
push:
44
branches:
5-
- master
5+
- main
66
pull_request:
77
permissions:
88
contents: read

‎README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ def hello_cloud_event(cloud_event):
104104
print(f"Received event with ID: {cloud_event['id']} and data {cloud_event.data}")
105105
```
106106

107-
> Your function is passed a single [CloudEvent](https://github.com/cloudevents/sdk-python/blob/master/cloudevents/sdk/event/v1.py) parameter.
107+
> Your function is passed a single [CloudEvent](https://github.com/cloudevents/sdk-python/blob/main/cloudevents/sdk/event/v1.py) parameter.
108108
109109
Run the following command to run `hello_cloud_event` target locally:
110110

@@ -302,7 +302,7 @@ After you've written your function, you can simply deploy it from your local mac
302302

303303
### Cloud Run/Cloud Run on GKE
304304

305-
Once you've written your function and added the Functions Framework to your `requirements.txt` file, all that's left is to create a container image. [Check out the Cloud Run quickstart](https://cloud.google.com/run/docs/quickstarts/build-and-deploy) for Python to create a container image and deploy it to Cloud Run. You'll write a `Dockerfile` when you build your container. This `Dockerfile` allows you to specify exactly what goes into your container (including custom binaries, a specific operating system, and more). [Here is an example `Dockerfile` that calls Functions Framework.](https://github.com/GoogleCloudPlatform/functions-framework-python/blob/master/examples/cloud_run_http)
305+
Once you've written your function and added the Functions Framework to your `requirements.txt` file, all that's left is to create a container image. [Check out the Cloud Run quickstart](https://cloud.google.com/run/docs/quickstarts/build-and-deploy) for Python to create a container image and deploy it to Cloud Run. You'll write a `Dockerfile` when you build your container. This `Dockerfile` allows you to specify exactly what goes into your container (including custom binaries, a specific operating system, and more). [Here is an example `Dockerfile` that calls Functions Framework.](https://github.com/GoogleCloudPlatform/functions-framework-python/blob/main/examples/cloud_run_http)
306306

307307
If you want even more control over the environment, you can [deploy your container image to Cloud Run on GKE](https://cloud.google.com/run/docs/quickstarts/prebuilt-deploy-gke). With Cloud Run on GKE, you can run your function on a GKE cluster, which gives you additional control over the environment (including use of GPU-based instances, longer timeouts and more).
308308

‎src/functions_framework/event_conversion.py

Lines changed: 1 addition & 6FA7 amp; 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@
2727

2828
# Maps background/legacy event types to their equivalent CloudEvent types.
2929
# For more info on event mappings see
30-
# https://github.com/GoogleCloudPlatform/functions-framework-conformance/blob/master/docs/mapping.md
30+
# https://github.com/GoogleCloudPlatform/functions-framework-conformance/blob/main/docs/mapping.md
3131
_BACKGROUND_TO_CE_TYPE = {
3232
"google.pubsub.topic.publish": "google.cloud.pubsub.topic.v1.messagePublished",
3333
"providers/cloud.pubsub/eventTypes/topic.publish": "google.cloud.pubsub.topic.v1.messagePublished",

0 commit comments

Comments
 (0)
0