1
0
mirror of https://codeberg.org/gitnex/GitNex synced 2025-02-02 04:16:58 +01:00

[Doc] update issue-template add pull-template (#359)

fix

add sugestions

fix Nr

fix what atom did wrong (automatism)

Add PR template

make link from contributing to the code-standards

Update issue_template

Co-authored-by: 6543 <6543@obermui.de>
Reviewed-on: https://gitea.com/gitnex/GitNex/pulls/359
Reviewed-by: M M Arif <mmarif@swatian.com>
This commit is contained in:
6543 2020-04-06 09:38:02 +00:00 committed by M M Arif
parent 1dc61af683
commit 9b9173e33b
4 changed files with 35 additions and 14 deletions

22
.gitea/issue_template.md Normal file
View File

@ -0,0 +1,22 @@
#### Description - describe the bug / feature / suggestion in brief :
#### Expected behaviour - describe what should be the expected result :
#### GitNex version :
#### Gitea setup :
* Version :
* If ssl used witch kind of cert is used :
* (if login issue) witch auth method :
#### Android version :
#### Screenshots - if any :
#### Logs - if any :

View File

@ -0,0 +1,8 @@
Please check the following:
1. Make sure you are targeting the `master` branch, pull requests on release branches are only allowed for bug fixes.
2. Read contributing guidelines: [CONTRIBUTING.md](https://gitea.com/GitNex/GitNex/src/branch/master/CONTRIBUTING.md)
3. Please follow the [Code-Standards](https://gitea.com/gitnex/GitNex/wiki/Code-Standards)
4. Describe what your pull request does and which issue youre targeting (create one if does not exist)
**You MUST delete the content above including this line before posting, otherwise your pull request will be invalid.**

View File

@ -7,6 +7,11 @@ Patches, enhancements, features are always welcome. The PR should focus on the s
Please ask if you are not sure about the scope of work to be submitted to avoid waste of time spent on the work. Please ask if you are not sure about the scope of work to be submitted to avoid waste of time spent on the work.
**Code Standards**
Please follow the code standards, this will help other developers to understand your code too.
It also helps maintaining the code afterwards.
It is documented in the Wiki: [Code-Standards](https://gitea.com/gitnex/GitNex/wiki/Code-Standards)
**How to submit a PR** **How to submit a PR**
Fork this repository. Pull the forked repository from your namespace to your local machine. Create new branch and work on the bug/feature/enhancement you would like to submit. Push it to your forked version. From there create Pull Request(PR) against **master** branch. Fork this repository. Pull the forked repository from your namespace to your local machine. Create new branch and work on the bug/feature/enhancement you would like to submit. Push it to your forked version. From there create Pull Request(PR) against **master** branch.

View File

@ -1,14 +0,0 @@
#### Description - describe the bug / feature / suggestion in brief :
#### Expected behaviour - describe what should be the expected result :
#### GitNex version :
#### Gitea version :
#### Android version :
#### Screenshots - if any:
#### Logs - if any :