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
MineAdmin is an open source project and we welcome anyone to participate in its development. If you would like to participate in development, please read the following.
9
+
MineAdmin is an open source project, and we welcome anyone to participate in its development. If you would like to participate in development, please read the following.
4
10
5
11
## Repository address
6
12
7
-
Currently the source code repository is hosted on Github, and the front-end and back-end source code in the gitee repository is used as a mirror repository. The code is automatically synchronized every day. We do not support any kind of code submission.
8
-
However, [documentation](https://doc.mineadmin.com/) is maintained on [code cloud repository](https://gitee.com/mineadmin/mineadmin-doc).
13
+
Currently, the codebase is hosted on GitHub. The front-end and back-end code in the Gitee repository **are** read-only mirror repositories, automatically synchronized every day. We **do not accept** code submissions on Gitee.
14
+
15
+
>**Note**: Starting from version 3.0, both the front-end and back-end source code are located in the `/web` directory of this repository.
@@ -26,48 +33,55 @@ However, [documentation](https://doc.mineadmin.com/) is maintained on [code clou
26
33
27
34
* We will release some pending features in issues, if you are interested, you can leave a comment in issues, we will reply as soon as possible.
28
35
* Comment replies help users who ask questions;
29
-
* According to the content of [issues](https://github.com/mineadmin/mineadmin/issues), propose a reasonable solution; go to fix the bug or realize the function, and take [pull request](https://github.com/mineadmin/mineadmin/pulls) to the MineAdmin repository.
36
+
* According to the content of [issues](https://github.com/mineadmin/mineadmin/issues), propose a reasonable solution; go to fix the bug or realize the function, and take [pull request](https://github.com/mineadmin/mineadmin/pulls) to the MineAdmin repository.
30
37
* Keep an eye on the progress and status of your own Pull Requests, in order to push your Pull Requests to be merged into the main repository as soon as possible;
31
38
* Conduct Code Review on other people's Pull Requests, and give your suggestions and opinions.
32
39
* Develop independent functional components based on others' or your own requirements;
33
40
* Improve the [documentation](https://gitee.com/mineadmin/mineadmin-doc) to provide better usage instructions.
34
41
35
42
### Pull Request Guidelines
36
43
37
-
Although we regularly release features for development, you are more than welcome to suggest features that you would like to implement. You can submit your ideas in [issues](https://github.com/mineadmin/mineadmin/issues) and we will reply as soon as possible whether we accept them or not.
44
+
Although we regularly release features for development, you are more than welcome to suggest features that you would like to implement. You can submit your ideas in [issues,](https://github.com/mineadmin/mineadmin/issues) and we will reply as soon as possible whether we accept them or not.
38
45
Before submitting an issue, please check if a similar issue has already been posted.
39
46
40
-
* fork this repository to your Github account;
47
+
* fork this repository to your GitHub account;
41
48
* The format of the commit message should be [File Name]: Info about commit. (e.g.) README.md: Fix xxx bugs
42
49
* Run `composer cs-fix` to format your code before committing it;
43
-
* Run `composer an` for static code checking before committing;
44
-
* Run `composer test` before submitting code.
50
+
* Run `composer analyse` for static code checking before committing;
51
+
* Run `composer test` before submitting code.
52
+
***Note:** ！！！Do NOT run unit tests on any of your production environments, as they will delete or modify data!！！！
45
53
* Make sure to create the PR as your functional branch, rather than committing changes directly on the master branch.
46
54
* If your PR fixes a bug, please provide a description of the bug.
0 commit comments