Skip to content

Conversation

@LucasJantschChitolina
Copy link

@LucasJantschChitolina LucasJantschChitolina commented Aug 24, 2025

Runs lint-staged, astro check, and registry build with required env vars (DEPLOY_PRIME_URL set to localhost - unsure if this is the best approach, open to feedback).

An example of the actions running can be seen in: https://github.com/LucasJantschChitolina/wds-shadcn-registry/actions/runs/17194290235/job/48774101967

closes #65

@netlify
Copy link

netlify bot commented Aug 24, 2025

‼️ Deploy request for wds-shadcn-registry rejected.

Name Link
🔨 Latest commit 9450da8

Copy link
Owner

@WebDevSimplified WebDevSimplified left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for taking so long to get back to you on this. I was out of town and then very busy. I left some comments on a few things that need changed/updated for this to work correctly.

- name: Install dependencies
run: npm ci

- name: Run lint-staged
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we break each linting and formatting task into its own job? This will ensure they all run in parallel and each will throw their own errors which means if the linting and formatting is broken we will get two errors instead of only one of them running and throwing an error.

run: npm ci

- name: Run lint-staged
run: npx lint-staged
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This command should be broken into two different jobs npx eslint ., and npx prettier --check .. npx lint-staged only runs on staged files which there will be none in the CI environment.

DEPLOY_PRIME_URL: https://localhost:4321
URL: https://wds-shadcn-registry.netlify.app

- name: Build registry
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't actually ensure the registry that is committed is the same as the one built by this command. We probably need to add a diff step to ensure the code in the registry folder doesn't change after running this since if it does change it means the registry is not being built before pushing.

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.

[feat]: Add GitHub actions for linting/building of registry

2 participants