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
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+9-9
Original file line number
Diff line number
Diff line change
@@ -4,11 +4,11 @@
4
4
5
5
Before you begin:
6
6
- Have you read the [code of conduct](CODE_OF_CONDUCT.md)?
7
-
- Check out the [existing issues](https://github.com/webdevnerdstuff/vue3-code-block/issues).
7
+
- Check out the [existing issues](https://github.com/webdevnerdstuff/vue-code-block/issues).
8
8
9
9
### Don't see your issue? Open one
10
10
11
-
If you spot something new, open an issue using a [template](https://github.com/webdevnerdstuff/vue3-code-block/issues/new/choose). We'll use the issue to have a conversation about the problem you want to fix.
11
+
If you spot something new, open an issue using a [template](https://github.com/webdevnerdstuff/vue-code-block/issues/new/choose). We'll use the issue to have a conversation about the problem you want to fix.
12
12
13
13
### Ready to make a change? Fork the repo
14
14
@@ -31,7 +31,7 @@ When you're done making changes and you'd like to propose them for review, open
31
31
### Your PR is merged!
32
32
Congratulations! The whole GitHub community thanks you. :sparkles:
33
33
34
-
Once your PR is merged, you will be proudly listed as a contributor in the [contributor chart](https://github.com/webdevnerdstuff/vue3-code-block/graphs/contributors).
34
+
Once your PR is merged, you will be proudly listed as a contributor in the [contributor chart](https://github.com/webdevnerdstuff/vue-code-block/graphs/contributors).
35
35
36
36
### Keep contributing as you use Vue3 CodeBlock
37
37
@@ -43,12 +43,12 @@ You can contribute to the Vue3 CodeBlock content and site in several ways. This
43
43
### :mega: Discussions
44
44
Discussions are where we have conversations.
45
45
46
-
If you'd like help troubleshooting a Vue3 CodeBlock PR you're working on, have a great new idea, or want to share something amazing you've learned, join us in [discussions](https://github.com/webdevnerdstuff/vue3-code-block/discussions).
46
+
If you'd like help troubleshooting a Vue3 CodeBlock PR you're working on, have a great new idea, or want to share something amazing you've learned, join us in [discussions](https://github.com/webdevnerdstuff/vue-code-block/discussions).
47
47
48
48
### :beetle: Issues
49
49
[Issues](https://docs.github.com/en/github/managing-your-work-on-github/about-issues) are used to track tasks that contributors can help with.
50
50
51
-
If you've found something in the content or the website that should be updated, search open issues to see if someone else has reported the same thing. If it's something new, open an issue using a [template](https://github.com/webdevnerdstuff/vue3-code-block/issues/new/choose). We'll use the issue to have a conversation about the problem you want to fix.
51
+
If you've found something in the content or the website that should be updated, search open issues to see if someone else has reported the same thing. If it's something new, open an issue using a [template](https://github.com/webdevnerdstuff/vue-code-block/issues/new/choose). We'll use the issue to have a conversation about the problem you want to fix.
52
52
53
53
### :hammer_and_wrench: Pull requests
54
54
A [pull request](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests) is a way to suggest changes in our repository.
@@ -66,10 +66,10 @@ You can browse existing issues to find something that needs help!
66
66
### Labels
67
67
Labels can help you find an issue you'd like to help with.
68
68
69
-
- The [`help wanted` label](https://github.com/webdevnerdstuff/vue3-code-block/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement) is for problems or updates that anyone in the community can start working on.
70
-
- The [`documentation` label](https://github.com/webdevnerdstuff/vue3-code-block/issues?q=is%3Aopen+is%3Aissue+label%3Adocumentation) is for problems or updates relating to the README.MD documentation.
71
-
- The [`bug` label](https://github.com/webdevnerdstuff/vue3-code-block/issues?q=is%3Aopen+is%3Aissue+label%3Abug) is for problems with the code and bugs.
72
-
- The [`enhancement` label](https://github.com/webdevnerdstuff/vue3-code-block/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement) is for
69
+
- The [`help wanted` label](https://github.com/webdevnerdstuff/vue-code-block/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement) is for problems or updates that anyone in the community can start working on.
70
+
- The [`documentation` label](https://github.com/webdevnerdstuff/vue-code-block/issues?q=is%3Aopen+is%3Aissue+label%3Adocumentation) is for problems or updates relating to the README.MD documentation.
71
+
- The [`bug` label](https://github.com/webdevnerdstuff/vue-code-block/issues?q=is%3Aopen+is%3Aissue+label%3Abug) is for problems with the code and bugs.
72
+
- The [`enhancement` label](https://github.com/webdevnerdstuff/vue-code-block/issues?q=is%3Aopen+is%3Aissue+label%3Aenhancement) is for
73
73
suggestions to improve the code or adding of additional features.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/BUG_REPORT.yaml
+1-1
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ body:
39
39
id: terms
40
40
attributes:
41
41
label: Code of Conduct
42
-
description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/webdevnerdstuff/vue3-code-block/blob/main/.github/CODE_OF_CONDUCT.md)
42
+
description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/webdevnerdstuff/vue-code-block/blob/main/.github/CODE_OF_CONDUCT.md)
43
43
options:
44
44
- label: I agree to follow this project's Code of Conduct
Copy file name to clipboardExpand all lines: dist/scss/README.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -5,22 +5,22 @@ If you would like to contribute any missing theme tab styles please follow the i
5
5
_I am not currently accepting any custom themes to be integrated into the plugin at this time._
6
6
7
7
## 🚀 Getting Started
8
-
Before you get started, please read the [Contributing](https://github.com/webdevnerdstuff/vue3-code-block/blob/main/.github/CONTRIBUTING.md) and [Contributor Covenant Code of Conduct](https://github.com/webdevnerdstuff/vue3-code-block/blob/main/.github/CODE_OF_CONDUCT.md) pages.
8
+
Before you get started, please read the [Contributing](https://github.com/webdevnerdstuff/vue-code-block/blob/main/.github/CONTRIBUTING.md) and [Contributor Covenant Code of Conduct](https://github.com/webdevnerdstuff/vue-code-block/blob/main/.github/CODE_OF_CONDUCT.md) pages.
9
9
10
10
1. Fork the repository.
11
11
2. Clone the forked repository to your local machine.
12
12
3. Create a new branch for your changes.
13
13
4. Install the node packages `pnpm i`. Please do not use `npm` or `yarn`.
14
14
5. Run the development server with the developer playground `pnpm play`.
15
-
6. You can view the demo site at the link provided by vite that will display in the console. Ex. `http://localhost:5173/vue3-code-block/`
16
-
7. The playground page will open automatically or can be viewed by adding `playground/` to the demo site link provided by vite that will display in the console. Ex. `http://localhost:5173/vue3-code-block/playground/`. The base site link will also be working.
15
+
6. You can view the demo site at the link provided by vite that will display in the console. Ex. `http://localhost:5173/vue-code-block/`
16
+
7. The playground page will open automatically or can be viewed by adding `playground/` to the demo site link provided by vite that will display in the console. Ex. `http://localhost:5173/vue-code-block/playground/`. The base site link will also be working.
17
17
18
18
## 📋 Additional notes
19
19
Make sure you are not adding a theme that already exists.
20
20
21
21
When selecting colors for the tabs, use colors from the themes stylesheet. Generally a green color for `success`, red color for `failed`. If the theme does not have a color for `success` or `failed`, use the default variables `--v-cb-success` and `--v-cb-failed`.
22
22
23
-
Do not change other variable colors. Please stick to the theme you are adding. If you have a suggestion for changing a variable color already defined, please open a [discussion](https://github.com/webdevnerdstuff/vue3-code-block/discussions). The reason we have the variables is to allow users to customize the colors to their liking if they do not like the defaults already created.
23
+
Do not change other variable colors. Please stick to the theme you are adding. If you have a suggestion for changing a variable color already defined, please open a [discussion](https://github.com/webdevnerdstuff/vue-code-block/discussions). The reason we have the variables is to allow users to customize the colors to their liking if they do not like the defaults already created.
24
24
25
25
Make sure your `css` and `scss` files are using tabbed spacing. When adding themes, do not change or alter any other files than the ones mentioned below. If you have a bug fix please make your changes in a separate branch and create a separate pull request.
0 commit comments