forked from ouihq/betterKabu
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
dfb752d
commit 6053931
Showing
1 changed file
with
1 addition
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -19,23 +19,15 @@ To change the color of the highlighting: Open the Extension on the digikabu.de w | |
- Custom highlighting | ||
- Time remaining until the next lesson | ||
|
||
## Chromium based special | ||
If you use the Extension from Github for chromium based browsers, use the "chromium-changes" branch instead of main. Because there are custom modifications for those browsers. | ||
|
||
# Contribution Guide | ||
|
||
## Intro | ||
|
||
If you want to contribute, you are free to do so. If you have any questions, you are free to do so. If you have found issues oder want to suggest features, you can submit that in GitHub. | ||
|
||
## Versions (>2.0.0) | ||
|
||
If there is a bug fix, the version increments in the last digit by one. If there is a new feature, the version increments in the second digit by one. | ||
|
||
## General | ||
|
||
For anything, create a new branch with the following naming scheme (featue/… | fix/… | refactor/…). After you're done, create a pull request, and we test it, or change some things and then merge it into main. For git commit messages please follow this guide: https://www.conventionalcommits.org/en/v1.0.0/. And the commit git e-mail should be the same as your GitHub e-mail. For further questions, please contact us. | ||
|
||
For anything, create a pull request with the naming scheme (featue/… | fix/… | refactor/…) and if avalible the reference to the issue, and we test it, or change some things and then merge it into main. For git commit messages please follow this guide: https://www.conventionalcommits.org/en/v1.0.0/. And the commit git e-mail should be the same as your GitHub e-mail. For further questions, please contact us. | ||
|
||
**contact: [email protected]** | ||
|
||
|