fix(repo): run publish gallery on main branch

[renefloor]

Submit a pull request

CLA

• I have signed the Stream CLA (required).
• The code changes follow best practices
• Code changes are tested (add some information if not applicable)

Description of the pull request

When merging the design system branch we forgot to update this target branch

Summary by CodeRabbit

• Chores
  • Updated the deployment pipeline configuration to publish the design system gallery from the main branch, ensuring timely updates to published documentation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cbdb4b8c-a4cc-44a7-906c-0ec581d96fb7

📥 Commits

Reviewing files that changed from the base of the PR and between 4579010 and d9f2076.

📒 Files selected for processing (1)

• .github/workflows/publish_gallery.yml

---

📝 Walkthrough

Walkthrough

The CI/CD workflow configuration for publishing the design system gallery was updated to trigger on commits to the main branch instead of main-design-system, modifying the branch activation condition for the pipeline without altering job logic or other trigger conditions.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/publish_gallery.yml	Modified push trigger branch filter from main-design-system to main

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 The gallery gate shifts with a click,
From side branch to main, so quick!
Now publishes flow down the primary stream,
A workflow adjustment, smooth as a dream. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix(repo): run publish gallery on main branch' clearly and specifically describes the main change: updating the workflow trigger branch from a design system branch to main.
Description check	✅ Passed	The description covers the core requirement by explaining why the change was made (design system branch merge required a workflow update) and confirms CLA compliance and code testing.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/publish-gallery-workflow

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 26.16%. Comparing base (4579010) to head (d9f2076).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #98   +/-   ##
=======================================
  Coverage   26.16%   26.16%           
=======================================
  Files         147      147           
  Lines        5251     5251           
=======================================
  Hits         1374     1374           
  Misses       3877     3877           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.