Skip to content

database: use explicit scope for read/update to avoid linting issues #1807

database: use explicit scope for read/update to avoid linting issues

database: use explicit scope for read/update to avoid linting issues #1807

Workflow file for this run

name: CI
on: [push]
jobs:
build_and_test_ubuntu:
name: Build/Test [Ubuntu]
runs-on: ubuntu-22.04
container:
image: paradajz168/opendeck-dev:latest
options: --user root
steps:
- name: Mark repository as safe
run: git config --global --add safe.directory /__w/OpenDeck/OpenDeck
- name: Pull the repository and submodules
uses: actions/checkout@v3
with:
fetch-depth: 0
submodules: recursive
- name: Build and test targets
run: |
git fetch --tags
./scripts/build_targets.sh --type=test
format:
name: Code formatting
runs-on: ubuntu-22.04
container:
image: paradajz168/opendeck-dev:latest
options: --user root
steps:
- name: Mark repository as safe
run: git config --global --add safe.directory /__w/OpenDeck/OpenDeck
- uses: actions/checkout@v3
with:
fetch-depth: 0
submodules: recursive
- name: Check formatting
run: |
make format
lint:
name: Code linting
runs-on: ubuntu-22.04
container:
image: paradajz168/opendeck-dev:latest
options: --user root
steps:
- name: Mark repository as safe
run: git config --global --add safe.directory /__w/OpenDeck/OpenDeck
- uses: actions/checkout@v3
with:
fetch-depth: 0
submodules: recursive
- name: Lint
run: |
./scripts/build_targets.sh --type=lint