Skip to content

ci: Use GITHUB_OUTPUT envvar instead of set-output command #145

ci: Use GITHUB_OUTPUT envvar instead of set-output command

ci: Use GITHUB_OUTPUT envvar instead of set-output command #145

Workflow file for this run

# Copyright (c) Meta Platforms, Inc. and affiliates.
#
# License found in the LICENSE file in the root directory
# of this source tree.
name: CI
on:
push:
branches: [ "main" ]
pull_request:
types: [opened, reopened, synchronize]
jobs:
build:
runs-on: ${{ matrix.os }}
strategy:
matrix:
os: [ubuntu-latest]
steps:
- uses: actions/checkout@v3
with:
# ct needs history to compare
fetch-depth: 0
- name: Build the Docker image
run: docker build ./proxy/ --tag whatsapp_proxy:$(date +%s)
- name: Set up Helm
uses: azure/setup-helm@v3
with:
version: v3.10.0
- uses: actions/setup-python@v4
with:
python-version: '3.9'
check-latest: true
- name: Helm - Set up chart-testing
uses: helm/[email protected]
- name: Helm - Run chart-testing (list-changed)
id: list-changed
run: |
changed=$(ct list-changed --target-branch ${{ github.event.repository.default_branch }})
if [[ -n "$changed" ]]; then
echo "changed=true" >> $GITHUB_OUTPUT
fi
- name: Helm - Run chart-testing (lint)
run: ct lint --target-branch ${{ github.event.repository.default_branch }}