Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up unused workflows #320

Merged
merged 1 commit into from
Jul 11, 2024
Merged

Clean up unused workflows #320

merged 1 commit into from
Jul 11, 2024

Conversation

robintown
Copy link
Member

We continuously deploy to https://compound.element.io using Cloudflare Pages, so we don't need to deploy to GitHub Pages as well. However, the workflow that did that was still useful for verifying that this actually builds, so I've kept that part.

Also, we don't release anything here to NPM.

We continuously deploy to https://compound.element.io using Cloudflare Pages, so we don't need to deploy to GitHub Pages as well. However, the workflow that did that was still useful for verifying that this actually builds, so I've kept that part.

Also, we don't release anything here to NPM.
Copy link

Deploying compound with  Cloudflare Pages  Cloudflare Pages

Latest commit: 03a880d
Status: ✅  Deploy successful!
Preview URL: https://7a1063e5.compound-5m4.pages.dev
Branch Preview URL: https://unused-workflows.compound-5m4.pages.dev

View logs

@jmartinesp
Copy link
Member

jmartinesp commented Jul 10, 2024

Won't this clash with element-hq/compound-design-tokens#88? They're modifying the same .github/workflows/automation.yaml in different ways. Maybe add this changes on top of those other ones?

EDIT: oh, I didn't realise it's a different repo, my bad 🤦 .

@robintown robintown merged commit dbe98e2 into main Jul 11, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants