Browse Source

[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: #359
Reviewed-by: M M Arif <mmarif@swatian.com>
tags/2.5.0-rc4
parent
commit
9b9173e33b
4 changed files with 35 additions and 14 deletions
  1. +22
    -0
      .gitea/issue_template.md
  2. +8
    -0
      .gitea/pull_request_template.md
  3. +5
    -0
      CONTRIBUTING.md
  4. +0
    -14
      issue_template.md

+ 22
- 0
.gitea/issue_template.md 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 :

+ 8
- 0
.gitea/pull_request_template.md 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 you’re 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.**

+ 5
- 0
CONTRIBUTING.md 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.

**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**
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.



+ 0
- 14
issue_template.md 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 :

Loading…
Cancel
Save