https://github.com/eished/simple-jira
React + TypeScript + Tailwindcss + Flowbite 技术实践：仿 Jira 看板项目. jira-dev-tool 配置
https://github.com/eished/simple-jira
flowbite jira jira-dev-tool react-hook react-route-6 react18 typescript
Last synced: 8 months ago
JSON representation
React + TypeScript + Tailwindcss + Flowbite 技术实践：仿 Jira 看板项目. jira-dev-tool 配置
- Host: GitHub
- URL: https://github.com/eished/simple-jira
- Owner: Eished
- Created: 2022-05-02T12:41:40.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2022-08-15T17:01:02.000Z (over 3 years ago)
- Last Synced: 2024-04-19T21:00:33.095Z (almost 2 years ago)
- Topics: flowbite, jira, jira-dev-tool, react-hook, react-route-6, react18, typescript
- Language: JavaScript
- Homepage: https://jira.iknow.fun
- Size: 2.43 MB
- Stars: 13
- Watchers: 2
- Forks: 3
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Simple Jira
Demo: [jira.iknow.fun](https://jira.iknow.fun)
[文档和笔记](./docs/readme.md)
## Available Scripts
**`yarn start`**
Frontend: `http://localhost:3000`
Msw Mock Backend: `http://localhost:3000/api`
**`yarn test`**
Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.
**`yarn build`**
Builds the app for production to the `build` folder.
**`yarn server`**
json-server
Json Server Mock Backend: `http://localhost:3003`
https://github.com/typicode/json-server#getting-started
**`yarn seed`**
Seeding `./__json_server_mock__/db.json`
## Commit Message
https://github.com/conventional-changelog/commitlint/tree/master/@commitlint/config-conventional
```
[
'build',
'chore',
'ci',
'docs',
'feat',
'fix',
'perf',
'refactor',
'revert',
'style',
'test'
];
```
```
echo "foo: some message" # fails
echo "fix: some message" # passes
```
https://nitayneeman.com/posts/understanding-semantic-commit-messages-using-git-and-angular/#motivation
### 👷 build
The `build` type (formerly known as `chore`) is used to identify **development** changes related to the build system (involving scripts, configurations or tools) and package dependencies.
### 💚 ci
The `ci` type is used to identify **development** changes related to the continuous integration and deployment system - involving scripts, configurations or tools.
### 📝 docs
The `docs` type is used to identify documentation changes related to the project - whether intended externally for the end users (in case of a library) or internally for the developers.
### ✨ feat
The `feat` type is used to identify **production** changes related to new backward-compatible abilities or functionality.
### 🐛 fix
The `fix` type is used to identify **production** changes related to backward-compatible bug fixes.
### ⚡️ perf
The `perf` type is used to identify **production** changes related to backward-compatible performance improvements.
### ♻️ refactor
The `refactor` type is used to identify **development** changes related to modifying the codebase, which neither adds a feature nor fixes a bug - such as removing redundant code, simplifying the code, renaming variables, etc.
### 🎨 style
The `style` type is used to identify **development** changes related to styling the codebase, regardless of the meaning - such as indentations, semi-colons, quotes, trailing commas and so on.
### ✅ test
The `test` type is used to identify **development** changes related to tests - such as refactoring existing tests or adding new tests.
## UI
https://flowbite.com/
https://flowbite-react.com/
## jira-dev-tool Configuration
[jira-dev-tool](/docs/readme.md#jira-dev-tool-mock-后端的配置)