Compare commits

..

No commits in common. '032191c15a4ae03bbb096caf4ae636d47429d688' and '563760a3e90da024ee991eaf00ca676c5423eea1' have entirely different histories.

@ -5,22 +5,18 @@ name: Build APP
on:
push:
paths:
- 'app/**'
# branches: [ master ]
# pull_request:
# branches: [ master ]
branches: [ master ]
pull_request:
branches: [ master ]
jobs:
build:
runs-on: ubuntu-latest
defaults:
run:
working-directory: ./app
strategy:
matrix:
node-version: [12.x]
node-version: [10.x, 12.x, 14.x, 15.x]
# See supported Node.js release schedule at https://nodejs.org/en/about/releases/
steps:

@ -1,54 +0,0 @@
# This is a basic workflow to help you get started with Actions
name: Build Firmware
# Controls when the action will run.
on:
# Triggers the workflow on push or pull request events but only for the master branch
push:
branches: [ master ]
paths-ignore:
- 'app/**'
# pull_request:
# branches: [ master ]
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
# This workflow contains a single job called "build"
build:
# The type of runner that the job will run on
runs-on: ubuntu-latest
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
# - name: Cache pip
# uses: actions/cache@v2
# with:
# path: ~/.cache/pip
# key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
# restore-keys: |
# ${{ runner.os }}-pip-
# - name: Cache PlatformIO
# uses: actions/cache@v2
# with:
# path: ~/.platformio
# key: ${{ runner.os }}-${{ hashFiles('**/lockfiles') }}
#
- name: Set up Python
uses: actions/setup-python@v1
- name: Install PlatformIO
run: |
python -m pip install --upgrade pip
pip install --upgrade platformio
# - name: Install library dependencies
# run: pio lib -g install 1
- name: Run PlatformIO
# run: platformio run
run: pio run -e esp32
Loading…
Cancel
Save