#1 setup next 13

fdhhhdjd · Oct 17, 2023 · bac27e3 · bac27e3
1 parent 72c1967
commit bac27e3
Show file tree

Hide file tree

Showing 6 changed files with 124 additions and 5 deletions.
diff --git a/.github/COMMIT_CONVENTION.md b/.github/COMMIT_CONVENTION.md
@@ -0,0 +1,58 @@
+# Git Commit Message Convention
+We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history.
+
+## Commit Message Format
+Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
+format that includes a **type**, a **scope** and a **subject**:
+
+```
+<type>(<scope>): <subject>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<footer>
+```
+
+The **header** is mandatory and the **scope** of the header is optional.
+
+Any line of the commit message cannot be longer 72 characters! This allows the message to be easier
+to read on GitHub as well as in various git tools.
+
+The footer should contain a [closing reference to an issue](https://help.github.com/articles/closing-issues-via-commit-messages/) if any.
+
+Samples: (even more [samples](https://github.com/bbulakh/tailwind-ecommerce/commits/main))
+
+### Revert
+If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
+
+### Type
+The type of the made changes. Should be one of:
+* **feat** - some feature development
+* **fix** - bug fix
+* **docs** - changes in documentation
+* **style** - changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+* **perf**: A code change that improves performance
+* **refactor** - changes those do not fix a bug or implement a feature. Simple refactoring
+* **test** - adding missing tests or correcting existing tests
+* **chore** - any other changes, not affecting code
+* **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
+
+### Scope
+The scope could be anything specifying the place of the commit change. For example core, admin-plugin, translation etc...
+
+### Subject
+The subject contains a succinct description of the change:
+
+* use the imperative, present tense: "change" not "changed" nor "changes"
+* don't capitalize the first letter
+* no dot (.) at the end
+
+### Body
+Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
+The body should include the motivation for the change and contrast this with previous behavior.
+
+### Footer
+The footer should contain any information about **Breaking Changes** and is also the place to
+reference GitHub issues that this commit **Closes**.
+
+**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml
@@ -0,0 +1,11 @@
+# These are supported funding model platforms
+github: [fdhhhdjd]# Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: user?u=65668237
+open_collective: # Replace with a single Open Collective username
+ko_fi: tientainguyen
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+custom: ["https://profile-forme.cf"]
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,19 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: fdhhdjd
+---
+
+Description:
+
+Environment:
+
+Steps to reproduce:
+
+Actual result:
+
+Expected result:
+
+Attachment:
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: feature
+assignees: fdhhhdjd
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -9,21 +9,22 @@
     "lint": "next lint"
   },
   "dependencies": {
+    "@material-tailwind/react": "^1.2.4",
     "@types/node": "20.8.6",
     "@types/react": "18.2.28",
     "@types/react-dom": "18.2.13",
     "autoprefixer": "10.4.16",
+    "clsx": "^1.2.1",
     "eslint": "8.51.0",
     "eslint-config-next": "13.5.5",
+    "lodash": "^4.17.21",
     "next": "13.5.5",
     "postcss": "8.4.31",
     "react": "18.2.0",
     "react-dom": "18.2.0",
-    "tailwindcss": "3.3.3",
-    "typescript": "5.2.2",
+    "react-icons": "^4.7.1",
     "tailwind-merge": "^1.8.1",
-    "clsx": "^1.2.1",
-    "@material-tailwind/react": "^1.2.4",
-    "react-icons": "^4.7.1"
+    "tailwindcss": "3.3.3",
+    "typescript": "5.2.2"
   }
 }