Fixing Github action for canary branch

[colinmurphy]

Tasks

• I have signed a Contributor License Agreement (CLA) with WP Engine.
• If a code change, I have written testing instructions that the whole team & outside contributors can understand.
• I have written and included a comprehensive changeset to properly document the changes I've made.

Description

Currently we cannot merge the canary branch - #2092

This should fix those issues.

Attaching screenshot from the first commit which also ran those actions for this branch

Related Issue(s):

Testing

Screenshots

Documentation Changes

Dependant PRs

[changeset-bot]

⚠️ No Changeset found

Latest commit: ebb6a3e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[moonmeister]

This is not how you fix this

[moonmeister]

What was the actual issue? The problem I saw last week was that I set this to ignore certain files.

    paths-ignore:
      - '**/*.md'
      - '**/*.php'

So making documentation and non-code changes meant these required checks never ran. Was there a different issue?