ICU-22707 Unicode 16 beta jun04 #53
Workflow file for this run
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Copyright (C) 2016 and later: Unicode, Inc. and others. | |
| # License & terms of use: http://www.unicode.org/copyright.html | |
| # | |
| # GitHub Actions workflow to ensure all required checks pass when they are attempted. | |
| # In other words, many checks are conditionally run, so use this workflow as a workaround | |
| # to a limitation in Github Actions in how required checks are enforced. Instead of | |
| # Github's naive behavior currently, this workflow only asserts that status=passing on | |
| # checks when they are run. | |
| name: Wait for Required Checks | |
| on: | |
| push: | |
| branches: | |
| - main | |
| - 'maint/maint*' | |
| pull_request: | |
| branches: '**' | |
| jobs: | |
| enforce-all-checks: | |
| runs-on: ubuntu-latest | |
| permissions: | |
| checks: read | |
| steps: | |
| - name: Wait for Triggered Required GH Checks | |
| uses: poseidon/wait-for-status-checks@6988432d64ad3f9c2608db4ca16fded1b7d36ead # v0.5.0 | |
| with: | |
| token: ${{ secrets.GITHUB_TOKEN }} | |
| # This is one large regex. The GHA parser for the YAML `>-` operator doesn't work as advertised, | |
| # so instead, this next best thing is to write out the regex pattern string directly | |
| match_pattern: "license.*|jira-ticket|single-commit|CI-ICU4J|CI-ICU4C|Test build of User Guide docs|copyright-scan|valid-UTF-8-and-no-BOM-check|icu4j-.*|icu4c-.*|gcc-.*|clang-.*|run-with-stubdata|u-.*|lstm-test|adaboost-test|testmap|internal-header-compilation|valid-UTF-8-and-no-BOM-check|uconfig-unit-tests.*|unicode-update-tools|lstm-icu4j.*|adaboost-icu4j.*|env-test.*" | |
| # For Azure Pipelines, each pipeline displays a check that represents the complete success of the pipeline. | |
| # It won't pass until all of the pipeline's checks pass. | |
| # For the ICU4J and ICU4C pipelines, this is called `CI-ICU4J` and `CI-ICU4C`. | |
| # These checks will return a "neutral" status, which this GH Action interprets as a failure. | |
| # Since the jobs are superfluous, they can be ignored. | |
| ignore: "CI-ICU4C,CI-ICU4J" |