Skip to content

Commit

Permalink
Merge branch 'main' into mgamis/automate-bug-bash-tests-phase-1
Browse files Browse the repository at this point in the history
  • Loading branch information
mgamis-msft authored Dec 2, 2024
2 parents e790432 + 51adc09 commit f6df5fb
Show file tree
Hide file tree
Showing 1,769 changed files with 23,795 additions and 63,893 deletions.
4 changes: 2 additions & 2 deletions .github/CODEOWNERS
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@
# Calling
/packages/calling-component-bindings/ @Azure/acs-ui-web-calling-reviewer-1 @Azure/acs-ui-web-calling-reviewer-2
/packages/calling-stateful-client/ @Azure/acs-ui-web-calling-reviewer-1 @Azure/acs-ui-web-calling-reviewer-2
/packages/storybook/stories/CallComposite/ @Azure/acs-ui-web-calling-reviewer-1 @Azure/acs-ui-web-calling-reviewer-2
/packages/storybook8/stories/CallComposite/ @Azure/acs-ui-web-calling-reviewer-1 @Azure/acs-ui-web-calling-reviewer-2
/samples/Calling/ @Azure/acs-ui-web-calling-reviewer-1 @Azure/acs-ui-web-calling-reviewer-2

# Chat
/packages/chat-component-bindings/ @Azure/acs-ui-web-chat-reviewer-1 @Azure/acs-ui-web-chat-reviewer-2
/packages/chat-stateful-client/ @Azure/acs-ui-web-chat-reviewer-1 @Azure/acs-ui-web-chat-reviewer-2
/packages/storybook/stories/ChatComposite/ @Azure/acs-ui-web-chat-reviewer-1 @Azure/acs-ui-web-chat-reviewer-2
/packages/storybook8/stories/ChatComposite/ @Azure/acs-ui-web-chat-reviewer-1 @Azure/acs-ui-web-chat-reviewer-2
/samples/Chat/ @Azure/acs-ui-web-chat-reviewer-1 @Azure/acs-ui-web-chat-reviewer-2
2 changes: 1 addition & 1 deletion .github/workflows/alpha-release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ jobs:
name: Build and publish alpha package
environment:
name: npm-alpha
runs-on: ubuntu-latest
runs-on: ${{ vars.RUNS_ON }}
permissions:
contents: write
id-token: write
Expand Down
4 changes: 2 additions & 2 deletions .github/workflows/breaking-change-check.yml
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ jobs:
# get matrix for ci-jobs
get_matrix:
name: Load CI Matrix Details
runs-on: ubuntu-latest
runs-on: ${{ vars.RUNS_ON }}
permissions: read-all
outputs:
matrix: ${{ steps.get-matrix.outputs.matrix }}
Expand All @@ -39,7 +39,7 @@ jobs:
check_breaking_changes:
needs: get_matrix
name: 'Check Breaking Changes (${{ matrix.flavor }})'
runs-on: ubuntu-latest
runs-on: ${{ vars.RUNS_ON }}
permissions: read-all
strategy:
matrix: ${{ fromJSON(needs.get_matrix.outputs.matrix) }}
Expand Down
6 changes: 3 additions & 3 deletions .github/workflows/ci.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

[ci.yml](./ci.yml) contains the [GitHub workflow](https://docs.github.com/en/get-started/getting-started-with-git/git-workflows) definition for presubmit tests in this repository.

All Pull Requests in this repository must pass the checks in this workflow before being merged into the `main` branch. The checks are distributed across several jobs. Each job runs on a seprate build agent. Most of them can run concurrently.
All Pull Requests in this repository must pass the checks in this workflow before being merged into the `main` branch. The checks are distributed across several jobs. Each job runs on a separate build agent. Most of them can run concurrently.

Many of checks build and test the library code in both the [`beta` and `stable` build flavors](../../docs/references/beta-only-features.md). For such jobs, we use a [job matrix](https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs) to run an instance of the job for each build flavor. The following high-level description of the checks calls out which checks are build-flavor aware.

Expand Down Expand Up @@ -31,13 +31,13 @@ Many of checks build and test the library code in both the [`beta` and `stable`
- Run some Playwright smoke tests against the sample application. These tests only sanity test the sample application. They are not as extensive as the browser tests in the job above.
- Upload any UI snapshot differences as GitHub workflow artifacts

- `build_storybook`: Build and test [storybook](../../packages/storybook/). This job is *not* build flavor aware. Storybook is always built using the `beta` build flavor.
- `build_storybook`: Build and test [storybook](../../packages/storybook8/). This job is *not* build flavor aware. Storybook is always built using the `beta` build flavor.
- Run linting tool `eslint`
- Build storybook using `webpack`.
- Run unit-tests.

- Informational jobs to track jest tests coverage (`compare_jest_tests_coverage`, `update_jest_coverage_report`): These jobs track the jest tests coverage (lines, functions, statements, branches) for `@azure/communication-react` built in the previous steps. Any differences in the coverage are reported as Pull Request comments, _but do not block Pull Request from being merged_. This jobs are build flavor aware.

- Informational jobs to track sample bundle size (`compare_base_bundle_stats`, `update_base_bundle_report`): These jobs track the expected bundle size of the sample applications built in the previous steps. Any differences in the size are reported as Pull Request comments, _but do not block Pull Request from being merged_. This job is not build flavor aware.
- Informational jobs to track sample bundle size (`compare_base_bundle_stats`, `update_base_bundle_report`): These jobs track the expected bundle size of the sample applications built in the previous steps. Any differences in the size are reported as Pull Request comments. If the differences are above a threshold, it will block the Pull Request from being merged. Pull Request owners can add a `significant bundle size change` tag to unblock the merge. This job is not build flavor aware.

- `check_failure`: This is a meta-job that only applies to _post-submit_ workflow run (which re-uses the same `ci.yml` definition). It opens a new GitHub issue in the repository if any fundamental step in the jobs above fails on post-submit workflow run, because it indicates a problem with the CI infrastructure or a bug in the product on `main`. This job is not build flavor aware.
Loading

0 comments on commit f6df5fb

Please sign in to comment.