目前我有一个工作看起来像这样在一个工作流程:
flutter_test:
name: Run flutter test and analyze
runs-on: ubuntu-latest
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
- uses: actions/setup-java@v1
with:
java-version: "12.x"
- uses: subosito/flutter-action@v1.5.3
with:
channel: "stable"
- name: Testing and analyzing paginablelistviewbuilder_example
run: cd example/paginablelistviewbuilder_example/ && flutter pub get && flutter analyze && flutter test
- name: Testing and analyzing paginablelistviewbuilder_example
run: cd example/paginablesliverchildbuilderdelegate_example/ && flutter pub get && flutter analyze && flutter test
- name: Testing and analyzing paginable
run: flutter pub get && flutter analyze && flutter test --coverage
- name: Upload coverage to Codecov
uses: codecov/codecov-action@v2
with:
files: coverage/lcov.info
可以看到,Testing and analyzing paginablelistviewbuilder_example
、Testing and analyzing paginablelistviewbuilder_example
和Testing and analyzing paginable
有不同的命令附加在&&
操作符上,这使得它有点长,难以阅读。
如果有一种方法可以将runs
分组,如以下假设:
- name: Testing and analyzing paginablelistviewbuilder_example
run: cd example/paginablelistviewbuilder_example/ flutter pub get
run: flutter analyze
run: flutter test
这将使工作流程更易于阅读。
可以使用管道运行多行命令
- name: Testing and analyzing paginablelistviewbuilder_example
run: |
cd example/paginablelistviewbuilder_example/ flutter pub get
flutter analyze
flutter test