Skip to content

Commit

Permalink
check: add flutter-main check
Browse files Browse the repository at this point in the history
The `check-flutter-main` job serves 2 purposes:
1. It checks that the code works with the flutter's latest main
   channel.
2. It checks that our code environment setup works with a typical
   Flutter SDK installation setup (via ~/flutter).
  • Loading branch information
chrisirhc authored and gnprice committed Apr 30, 2024
1 parent e9d04ea commit 37a5bf7
Showing 1 changed file with 33 additions and 0 deletions.
33 changes: 33 additions & 0 deletions .github/workflows/ci-flutter-main.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# The `check-flutter-main` job serves 2 purposes:
# 1. It checks that the code works with the flutter's latest main
# channel.
# 2. It checks that tools/check and our related scripts don't embed
# any hidden assumptions that the Flutter SDK lives at vendor/flutter/.
name: CI

on: push

jobs:
check-flutter-main:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3

- name: Clone Flutter SDK
# We can't do a depth-1 clone, because we need the most recent tag
# so that Flutter knows its version and sees the constraint in our
# pubspec is satisfied. It's uncommon for flutter/flutter to go
# more than 100 commits between tags. Fetch 1000 for good measure.
run: |
git clone --depth=1000 https://github.com/flutter/flutter ~/flutter
TZ=UTC git --git-dir ~/flutter/.git log -1 --format='%h | %ci | %s' --date=iso8601-local
echo ~/flutter/bin >> "$GITHUB_PATH"
- name: Download Flutter SDK artifacts (flutter precache)
run: flutter precache --universal

- name: Download our dependencies (flutter pub get)
run: flutter pub get

- name: Run tools/check
run: TERM=dumb tools/check --all --verbose

0 comments on commit 37a5bf7

Please sign in to comment.