ci: migrate from CircleCI to Github Actions

[ze-flo]

Description

Migrate from CircleCI to Github Actions! 🤖 🚀

Detail

• Converts CCI's to GHA config
• Leverage parallel jobs to speed up workflow
• Follows approach to "build first, discard if tests fail"
• Persists only the necessary files across jobs using actions/upload-artifact@v4 + actions/download-artifact@v4
• Reduces average CI workflow duration on "non-main" branches from ~16min to ~11min (~30% faster! 🚀 )

Checklist

• [ ] 👌 design updates will be Garden Designer approved (add the designer as a reviewer)
• [ ] 🌐 demo is up-to-date (npm start)
• [ ] ⬅️ renders as expected with reversed (RTL) direction
• [ ] 🤘 renders as expected with Bedrock CSS (?bedrock)
• [ ] 💂‍♂️ includes new unit tests. Maintain existing coverage (always >= 96%)
• [ ] ♿ tested for WCAG 2.1 AA accessibility compliance
• [ ] 📝 tested in Chrome, Firefox, Safari, and Edge

[ze-flo]

Stores content of packages/**/dist/ for test and publish jobs.

To (hopefully 😅) stay within the 500MB storage monthly allowance, we can explicitly set retention-days in the config:

Ex:

Suggested change

	- name: Upload dist artifacts
	uses: actions/upload-artifact@v4
	with:
	name: dist-artifact
	path: packages/**/dist
	- name: Upload dist artifacts
	uses: actions/upload-artifact@v4
	with:
	name: dist-artifact
	path: packages/**/dist
	retention-days: 7

Or globally define it from the settings page.

Which way do you prefer?

[geotrev]

Is this something we had set previously for CCI? I didn't see an equivalent, so I could go either way. The config route does feel more obvious for us to easily grok in the future, but the settings live independent of commit history.

[jzempel]

Let's definitely rely on the setting rather than specify here. I want to be able to control this outside the scope of a PR.

[jzempel]

All of these CI workflows should only happen on pull_request. That's the typical setting for all CircleCI repos. We just turned it off temporarily on react-components because there was no way to get next to build in addition to main.

[geotrev]

Does this config/GHA now allow us to only build on PR for select branches? 🤞🏻

[ze-flo]

Yes, it supports it.

https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#running-your-pull_request-workflow-based-on-the-head-or-base-branch-of-a-pull-request

on:
  pull_request:
    branches:
      - 'releases/**'

[jzempel]

Let's definitely rely on the setting rather than specify here. I want to be able to control this outside the scope of a PR.

[coveralls]

coverage: 96.374%. remained the same
when pulling 00a4e8a on ze-flo/CCI-to-GHA
into 44b5263 on main.

[ze-flo]

To clarify, this will only trigger following a push event.

For push events, github.ref looks something like this refs/heads/{branch}

For pull_request events, github.ref > refs/pull/{PR#}/merge

[coveralls]

coverage: 96.374%. remained the same
when pulling b5240e0 on ze-flo/CCI-to-GHA
into 44b5263 on main.

[coveralls]

coverage: 96.374%. remained the same
when pulling ded342c on ze-flo/CCI-to-GHA
into 44b5263 on main.

[coveralls]

coverage: 96.374%. remained the same
when pulling 02ffe95 on ze-flo/CCI-to-GHA
into 44b5263 on main.

[jzempel]

Nice work @ze-flo. I'll plan to continue on with this PR in prep for final transition away from CircleCI

[jzempel]

This condition is fine for now, but we'll need to allow version maintenance branches (i.e. v7, v8, etc) as well, so may need to weigh the idea of removing and relying solely on Lerna's allowBranch config.