[core] Ignore unrelated folders from github actions

[siriwatknp]

Ref: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-excluding-paths.

The ci.yml github action is all about packages check which is not related to docs and examples folders. This PR will speed up the CI check.

How to test?

I think we have to merge this one and open a fake PR that contains changes in docs/examples to test if the ignore works.

---

• I have followed (at least) the PR section of the contributing guide.

[mui-bot]

	Messages
📖	Netlify deploy preview: https://deploy-preview-35028--material-ui.netlify.app/

No bundle size changes

Generated by 🚫 dangerJS against cb8901d

[michaldudak]

I think this could cause a problem because CI / test-dev is a required check and, according to GitHub docs, when skipped, it'll stay in a Pending state forever (see the note under https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-including-paths).

There is a workaround described in https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks

[siriwatknp]

I think this could cause a problem because CI / test-dev is a required check and, according to GitHub docs, when skipped, it'll stay in a Pending state forever (see the note under https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-including-paths).

There is a workaround described in https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks

Oh, nice. Forgot about the check.

[siriwatknp]

@michaldudak please review again.

[michaldudak]

This should do the trick. Let's test it in action.

[siriwatknp]

🎉 It works! #35062

[michaldudak]

@siriwatknp There's a problem with running checks in PRs that change just the docs. See #35076
I think the source of the issue is the name of the job - it should be named the same as the required check (test-dev in this case).
However, I wonder if specifying it for:

pull_request:
    paths:
      - 'docs/**'
      - 'examples/**'

won't trigger the "fake" action also for PRs that change both the docs and other code. We'll have two jobs with the same name running - I don't know if this can cause any problems.

[oliviertassinari]

@siriwatknp what do you think about moving these tests to CircleCI? The value could be about having a single tool to run the CI. This means a single place to gather analytics about it, a single learning curve, or billing. For example, we could allocate larger machines.

Regarding only running based on the file changed, we could copy

material-ui/.circleci/config.yml

Lines 167 to 168 in 9d94f27

	if [ $FOLDER_COMMIT = $LATEST_COMMIT ]; then
	echo "changes, let's run the tests"

[siriwatknp]

@siriwatknp what do you think about moving these tests to CircleCI? The value could be about having a single tool to run the CI. This means a single place to gather analytics about it, a single learning curve, or billing. For example, we could allocate larger machines.

Regarding only running based on the file changed, we could copy

material-ui/.circleci/config.yml

Lines 167 to 168 in 9d94f27

	if [ $FOLDER_COMMIT = $LATEST_COMMIT ]; then
	echo "changes, let's run the tests"

Hey, I think that's another topic. My first intention is to skip the tests for non-related changes, not moving them to another provider.

[oliviertassinari]

@siriwatknp My thought was that the day-to-day problem is that this CI task is the slowest. On CircleCI, we could give the environment that runs these scripts more CPUs, the task would no longer be the slowest one. Skipping unnecessary work sounds great too 👍