You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge branch 'main' of github.com:HubbeDev/shadcn-svelte into feat/tasks-example
* 'main' of github.com:HubbeDev/shadcn-svelte: (45 commits)
fix required form select props (huntabyte#359)
Add colorscheme (huntabyte#358)
fix: form example typo (huntabyte#357)
Update dependencies (huntabyte#356)
Fix file input button text not visible in darkmode (huntabyte#353)
Stop scroll to top while navigating between examples in doc. (huntabyte#355)
try to fix lockfile (huntabyte#354)
fix pnpm lockfile
fix: check icon in checkbox is off-center (huntabyte#330)
fx: add the special `<alpha-value>` placeholder (huntabyte#341)
Footer no longer has a border (huntabyte#339)
Use regular click event (huntabyte#328)
Fix support rule (huntabyte#326)
Fixes `build:registry` script (huntabyte#327)
Fix disabled checkbox styles (huntabyte#307)
fix toggle doc code snippets (huntabyte#316)
fix: slate theme missing % character from ring color value (huntabyte#314)
Docs: Change CardTitle -> Card.Title (huntabyte#303)
chore: remove tailwindcssAnimate from docs (huntabyte#299)
fixing the typo (huntabyte#296)
...
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug_report.yml
+38-34
Original file line number
Diff line number
Diff line change
@@ -3,37 +3,41 @@ name: 🐛 Bug Report
3
3
description: Report an issue or bug
4
4
labels: ["type: bug"]
5
5
body:
6
-
- type: textarea
7
-
attributes:
8
-
label: Current Behavior
9
-
description: A description of what you're experiencing.
10
-
validations:
11
-
required: true
12
-
- type: textarea
13
-
attributes:
14
-
label: Expected Behavior
15
-
description: A description of what you're experiencing.
16
-
validations:
17
-
required: true
18
-
- type: textarea
19
-
attributes:
20
-
label: Steps To Reproduce
21
-
description: Describe how to reproduce the issue.
22
-
placeholder: |
23
-
1. Using this component...
24
-
2. With these properties...
25
-
3. Click '...'
26
-
4. See error...
27
-
validations:
28
-
required: true
29
-
- type: input
30
-
id: reproduction
31
-
attributes:
32
-
label: Link to Reproduction / Stackblitz
33
-
- type: textarea
34
-
attributes:
35
-
label: More Information
36
-
description: |
37
-
Provide relevant links or additionl information.
38
-
validations:
39
-
required: false
6
+
- type: markdown
7
+
attributes:
8
+
value: |
9
+
Before submitting a bug report, ensure you're running the latest version of the dependencies (`bits-ui` & `formsnap`/`sveltekit-superforms` if you're using forms). If you have a question, please ask it in the [Discussions](https://github.com/huntabyte/shadcn-svelte/discussions) or [Discord](https://hbyt.us/discord), not here.
10
+
- type: textarea
11
+
attributes:
12
+
label: Current Behavior
13
+
description: A description of what you're experiencing.
14
+
validations:
15
+
required: true
16
+
- type: textarea
17
+
attributes:
18
+
label: Expected Behavior
19
+
description: A description of what you're experiencing.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+29-22
Original file line number
Diff line number
Diff line change
@@ -6,41 +6,48 @@ We appreciate your interest in contributing. This guide will help you get starte
6
6
7
7
-[Contributing to shadcn-svelte](#contributing-to-shadcn-svelte)
8
8
-[Table of Contents](#table-of-contents)
9
+
-[Ways to contribute](#ways-to-contribute)
10
+
-[How to contribute](#how-to-contribute)
9
11
-[Questions](#questions)
10
-
-[Contributing](#contributing)
11
-
-[Submitting a Pull Request](#submitting-a-pull-request)
12
12
-[License](#license)
13
13
14
-
## Questions
15
-
16
-
If you have questions about the project, please start a new discussion in the [Discussions](https://github.com/huntabyte/shadcn-svelte/discussions), or join the [Discord](https://discord.gg/SRbSSrvXug) and ask your question under the `shadcn-svelte` -> `shadcn-support` channel.
17
-
18
-
## Contributing
14
+
## Ways to contribute
19
15
20
16
This project is open to contributions from the community.
21
17
22
18
We welcome contributions in the following areas:
23
19
24
-
-**Feedback**: We're always looking for feedback on the project. If you have any suggestions or ideas, please open an issue to discuss it.
25
-
-**Support**: If you feel confident in your ability to help others with their questions, please join the [Discord](https://discord.gg/SRbSSrvXug) and help out in the `shadcn-svelte` -> `shadcn-support` channel.
26
-
-**Feature enhancements**: If you have an idea for a new feature, please open an issue to discuss it before starting work on it to make sure it aligns with the project roadmap and you don't end up wasting your time.
27
-
-**Documentation improvements**: See a typo or broken link? Or do you think the documentation could be improved in some other way? Please open an issue to discuss it before making any changes.
28
-
-**Code optimizations**: If you see a way to improve the code, please open an issue to discuss it before making any changes.
20
+
-**Feedback**: We're always looking for feedback on the project. If you have any suggestions, ideas, please open an issue to discuss it. One thing that should be noted is that this project is a port of `shadcn/ui`, meaning we won't be adding new components to this project unless they are added to `shadcn/ui` first.
21
+
-**Support**: If you feel confident in your ability to help others with their questions, please join the [Discord](https://discord.gg/SRbSSrvXug) and help out in the `libs` -> `shadcn-support` channel, or answer questions asked in [Discussions](https://github.com/huntabyte/shadcn-svelte/discussions).
22
+
-**Documentation improvements**: See a typo or broken link? Or do you think the documentation could be improved in some other way? If it's a typo/broken link, feel free to open a PR. If the change would involve more than a few line changes, please open an issue to discuss it first before spending time on it.
23
+
-**Code optimizations**: If you see a way to improve the code, please open an issue to discuss it.
24
+
25
+
## How to contribute
29
26
30
-
## Submitting a Pull Request
27
+
This project operates using a process that makes maintaining the project less stressful, while also preventing wasted time and effort on contributions that may not be merged into the project.
31
28
32
-
We use pull requests to propose changes to the project. The process generally goes like this:
29
+
Here's what the process looks like:
33
30
34
-
1. A user opens an issue to discuss a new feature or to report a bug
35
-
2. A maintainer reviews the issue and may label it as `status: needs owner`
36
-
3. The issues author can volunteer to work on the issue, or someone else can
37
-
4. A maintainer assigns the issue to whoeever volunteers to work on it
38
-
5. The issue owner submits a pull request to address/resolve the issue
39
-
6. A maintainer reviews the pull request and if no changes are needed, merges it into the main repository
31
+
1. A user opens an issue to report a bug, request a new feature, or propose a change
32
+
2. A maintainer reviews the issue and assigns it a status label
33
+
1.`needs owner` - the issue is ready to be worked on, but no one has volunteered to work on it yet. If you would like to work on the issue, please leave a comment on the issue to let us know along with a brief description of how you plan to address the issue (if it's not already clear from the issue description).
34
+
2.`accepted` - the issue has been assigned to someone and they are working on a solution for it.
35
+
3.`duplicate` - the issue is a duplicate of another issue. The issue will be closed and a link to the original issue will be provided.
36
+
4.`blocked` - the issue is blocked by another issue either within this project or another.
37
+
5.`revisions needed` - the issue requires additional information or reproduction details before it will be considered for implementation/fix.
38
+
6.`under review` - further discussion is needed before a decision can be made on how to proceed with the issue.
39
+
3. The issue author can volunteer to work on the issue within the issue itself, or someone else can volunteer to work on it.
40
+
4. A maintainer assigns the issue to whoever volunteers to work on it and becomes the "owner" of the issue.
41
+
5. The issue owner submits a pull request to address/resolve the issue.
42
+
6. A maintainer reviews the pull request and if no revisions are needed, adds the changesets (if required) and merges it into the main repository.
40
43
41
-
**Note:** Do not submit a pull request until a relevant issue has been opened and assigned to you, otherwise, you may end up wasting time on work that may not be merged into the project.
44
+
**NOTE:** Do not submit a pull request for anything other than minor documentation/typo fixes without first opening an issue and having it assigned to you. We don't want you to waste time on something that may not be merged/accepted.
45
+
46
+
To volunteer to solve someone else's issue, please leave a comment on the issue to let us know that you'd like to work on it, along with a brief description of how you plan to address the issue (if it's not already clear from the issue description), and we'll assign the issue to you.
47
+
48
+
## Questions
42
49
43
-
To volunteer to solve someone else's issue, please leave a comment on the issue to let us know that you'd like to work on it, along with a brief description of how you plan to address the issue.
50
+
If you're looking to contribute and have questions about the process or the codebase in general, feel free to ask in the [Discord](https://hbyt.us/discord) in the `libs`->`shadcn-chat` channel!
0 commit comments