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

Feat/rules #230

Open
wants to merge 15 commits into
base: main
Choose a base branch
from
Open

Feat/rules #230

wants to merge 15 commits into from

Conversation

mhhnn
Copy link
Collaborator

@mhhnn mhhnn commented Aug 17, 2024

Linked Issue

Closes #{issueNumber}

Description

{description}

Changsets

Instructions: Changesets automate our changelog. If you modify files in /packages/ui, run pnpm run changeset in the root of the monorepo, follow the prompts, then commit the markdown file. Changes that add features should be minor while chores and bugfixes should be patch. Please prefix the changeset message with feat:, fix: or chore:.

Checklist

Please read and apply all contribution requirements.

  • This PR targets the main branch
  • Documentation reflects all relevant changes
  • Branch is prefixed with: docs/, feat/, chore/, fix/
  • Ensure Svelte and Typescript linting is current - run turbo lint
  • Ensure Biome linting is current - run turbo format
  • All test cases are passing - run turbo test
  • Includes a changeset (if relevant; see above)

Commit message format

This project requires at least one commit per PR to follow the below format.
Commit type: [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test]

Commit message Release type
fix(module): short description of change Patch Release
feat(module): short description of change Feature Release
feat(module): short description of change

BREAKING CHANGE: Long description of what is breaking
Breaking Release
ci(module): short description of change Feature Release

Copy link

changeset-bot bot commented Aug 17, 2024

⚠️ No Changeset found

Latest commit: 2bca15d

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

Copy link

vercel bot commented Aug 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
spectacular-console ❌ Failed (Inspect) Aug 26, 2024 2:56pm
spectacular-docs ❌ Failed (Inspect) Aug 26, 2024 2:56pm
spectacular-web ❌ Failed (Inspect) Aug 26, 2024 2:56pm

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.

1 participant