Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Kd/add bountysource (#14323) | Kyle D | 2021-01-13 | 1 | -0/+1 |
| | | | | | * Add bountysource to Sponsors link * Add badge to readme | ||||
* | Add FAQ link to Issue template (#14020) | 6543 | 2020-12-16 | 1 | -2/+3 |
| | |||||
* | Config lock bot (#13624) | 6543 | 2020-11-18 | 1 | -0/+23 |
| | | | | | * config lock bot * Update .github/lock.yml | ||||
* | add more clarification to the issue-template.md (#13235) | zeripath | 2020-10-21 | 1 | -0/+6 |
| | | | | | Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: techknowlogick <techknowlogick@gitea.io> | ||||
* | Remove not relevant option from issue template (#13188) | mrsdizzie | 2020-10-17 | 1 | -1/+0 |
| | | | | | | | Almost every use of "Not relevant" I see is the opposite -- it is relevant to have an example on try.gitea.io and often we can't do anything until the user provides one. Remove the not-relevant option so people have to decide yes/no if they are going to attempt to reproduce it which will hopefully encourage them to do so in simple cases. For actual not-relevant issues No should be a fine answer as well as it would be clear to us when you can't reproduce an example there. Hopefully this will encourage more examples when people file issues which would lead to quicker fixes. | ||||
* | Improve stale message (#9920) | Antoine GIRARD | 2020-01-22 | 1 | -4/+5 |
| | | | | | | | | * Improve stale nessage * Update .github/stale.yml Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com> | ||||
* | Display Github support button (#7343) | Antoine GIRARD | 2019-07-02 | 1 | -0/+1 |
| | | | This need an option to be enabled on repo : https://help.github.com/en/articles/displaying-a-sponsor-button-in-your-repository | ||||
* | Add security note to issue template (#6281) | John Olheiser | 2019-03-08 | 1 | -2/+4 |
| | |||||
* | Force the PR close time to 60 days (#5770) | Antoine GIRARD | 2019-01-19 | 1 | -0/+1 |
| | | | | | Like the comment that is posted. Ex: https://github.com/go-gitea/gitea/pull/4749 is closed after 2 weeks and not 2 months | ||||
* | Create stale bot config (#5243) | Antoine GIRARD | 2018-12-20 | 1 | -0/+52 |
| | |||||
* | Comment help text for issues (#2281) | Patrick G | 2017-08-09 | 1 | -7/+9 |
| | |||||
* | Add link to forum in issue template (#2070) | Jonas Östanbäck | 2017-06-28 | 1 | -2/+2 |
| | |||||
* | Update links to Discord server | Jonas Östanbäck | 2017-06-11 | 1 | -1/+1 |
| | |||||
* | Add MSSQL to issues template (#1171) | esell | 2017-03-10 | 1 | -0/+1 |
| | |||||
* | Fix grammar (#1158) | Patrick G | 2017-03-09 | 1 | -5/+5 |
| | |||||
* | Add Screenshot-secion to IssueTemplate.md (#939) | Kim "BKC" Carlbäcker | 2017-02-17 | 1 | -0/+5 |
| | | | For `UI`-bugs we usually require a Screenshot to debug it :wink: | ||||
* | Replace pull request with issue at issue_template (#547) | Bwko | 2016-12-31 | 1 | -1/+1 |
| | |||||
* | Update example install url from try.gogs.io to try.gitea.io (#385) | Sandro Santilli | 2016-12-15 | 1 | -0/+4 |
| | | | | | | | | * Update example install url from try.gogs.io to try.gitea.io * Ask if issue can be reproduced on try.gitea.io * Link try.gitea.io to the README | ||||
* | Unified GitHub templates accross all projects | Thomas Boerger | 2016-11-28 | 4 | -34/+26 |
| | |||||
* | Review issue and pull templates, drop unused contributing file | Sandro Santilli | 2016-11-05 | 3 | -82/+19 |
| | | | | The CONTRIBUTING.md from root dir will be used by github | ||||
* | Change import reference to match gitea instead of gogs (#37) | Rémy Boulanouar | 2016-11-03 | 2 | -4/+4 |
| | |||||
* | Replace gogs.io http links with https version (#3386) | rugk | 2016-08-05 | 1 | -1/+1 |
| | |||||
* | #3348 always use relative avatar link in the template | Unknwon | 2016-08-05 | 1 | -3/+4 |
| | |||||
* | Minor fix for pull request template [CI SKIP] | Unknwon | 2016-07-28 | 1 | -1/+1 |
| | |||||
* | Update GitHub templates | Unknwon | 2016-07-28 | 2 | -10/+17 |
| | |||||
* | Update locales | Unknwon | 2016-03-23 | 1 | -1/+1 |
| | |||||
* | ISSUE_TEMPLATE: suggestion to test at try.gogs.io | Lubomir I. Ivanov | 2016-03-02 | 1 | -0/+4 |
| | | | | | | | | | | | | | I've noticed that a lot of issues cannot be reproduced on http://try.gogs.io, which either hints about specific database type problems or hints about bugs which are already solved in the newer version (as http://try.gogs.io is usually a newer build). This patch adds the suggestion to test the issue at http://try.gogs.io in the Github "issue template". The user can answer: "Yes", "No", "Not relevant". "Not relevant" is an option where testing on http://try.gogs.io makes no sense as the bug is unrelated to the Web UI or is very specific in nature. | ||||
* | Prepare to release | Unknwon | 2016-02-24 | 1 | -0/+2 |
| | |||||
* | Removed duplicate of paragraph | Bart | 2016-02-21 | 1 | -4/+0 |
| | |||||
* | Add issue and pull request template | Unknwon | 2016-02-17 | 3 | -0/+87 |