aboutsummaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
2023-02-20Improve pull_request_template.md (#22888)Jason Song
Update `pull_request_template.md` because: - It's a kind idea to hide the tips. However, it's easier to include them in the commit message by mistake when you cannot see them. Check `git log | grep 'Please check the following:'`. So don't hide it, expose it and help fix it. - "for backports" is much clearer than "for bug fixes". I saw someone post a PR to a release branch because they believed it was the right way for a bugfix. - "Allow edits by maintainers", or we have to ask the contributor to update the branch and they could be confused. - Remind the contributor that the words could be included in the commit message, to avoid some words like "Hello", "Sorry". If they really need them, they can separate them with a line, like: ```markdown Close #xxxx Because ... Then ... Finally ... --- Hello, this is my first time opening a pull request. Sorry for any mistakes. ``` And the merger should be careful, check and delete the extra content before merging. --------- Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2022-06-07update discord invite (#19907)Eugene
2022-05-15Disable blank issues (#19717)John Olheiser
2022-03-21Reorder issue templates and automatically add labels (#18875)delvh
* Reorder bug-report.yaml * Add bug label on bug-report.yaml * Add feature label on feature-request.yaml * Reorder ui.bug-report.yaml * Apply suggestions Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: zeripath <art27@cantab.net>
2022-02-10Make the proformas clearer that we need DEBUG logs (#18700)zeripath
It is ridiculous how few of our bug reporter are giving us DEBUG level logs. This has to change and I think the proforma is not making it clear enough that they have to give us these logs. This PR changes the issue proformas to tell people to give us these logs. Signed-off-by: Andrew Thornton <art27@cantab.net>
2022-01-13Fix documents for development and bug report (#18249)wxiaoguang
2021-12-24Fix various typos of software names (#18083)qwerty287
* `git` -> `Git` * `Github` and `github` -> `GitHub` * `crowdin` -> `Crowdin` * `git-lfs` -> `Git LFS` * `githooks`, `git hooks`, `git-hooks` -> `Git Hooks` * `discord` -> `Discord` * `2fa` -> `2FA` * `gitlab` and `Gitlab` -> `GitLab` * `web hook` -> `webhook` * `linux` -> `Linux` * `sqlite` -> `SQLite` * `MYSQL` and `mysql` -> `MySQL` * rename refs to `master` branch -> `main` * Fix English grammar
2021-11-02hide note message for pull request template (#17529)a1012112796
Co-authored-by: John Olheiser <john.olheiser@gmail.com>
2021-09-29Fix wording in issue template (#17176)silverwind
There was a typo `systemm` here. I opted to just remove the superfluos word altogether.
2021-09-15Issue template form (#16349)Gabriel
* Create issue template using new format This issue template has been based off of the current issue creation workflow defined in the ISSUE_TEMPLATE.md file This commit allows for that issue template (which is a legacy method of creating an issue) to be deleted * Delete old issue template file This commit deletes the old issue template file, as it is both legacy and replaced by ISSUE_TEMPLATE/issue.yaml * Adjust file upload and remove code of conduct checkbox * Block blank issue creation * Update feedback Removed most requirements Updated prompt to include instruction to state whether using try.gitea.io Added default value to Gitea version * Create Feature Request issue form * Update and rename issue.yaml to bug-report.yaml * Enable blank issue creation Co-authored-by: a1012112796 <1012112796@qq.com> * Update config.yaml * Remove default & placeholder from Gitea version * Create issue template in .gitea directory * Add relevant bug report message to feature request * Adjust name to remove banner There is a banner that tells you to create a config.yml when you already have a config.yaml Renaming the file stops this from occurring. * Add UI bug report form * Remove unnecessary question Co-authored-by: a1012112796 <1012112796@qq.com> Co-authored-by: techknowlogick <techknowlogick@gitea.io> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lauris BH <lauris@nix.lv>
2021-05-22Update pull_request_template.md (#15948)Ikko Ashimine
Branch name - master -> main
2021-02-18Issue template addition: Are you using Gitea behind CloudFlare? (#14098)wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf
* chore: are you using Gitea behind CloudFlare since more often than not CF appears to serve stale cache and cause troubles, I'd argue it might be helpful to ask about it in this here issue template * implement suggestion: change question to comment * as per @techknowlogick's suggestion * chore: edit comment * implement @mrsdizzie's suggestion * as the comment grows, rather span multiple lines * Gitea --> gitea to match case used in the rest of the template Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2021-01-13Kd/add bountysource (#14323)Kyle D
* Add bountysource to Sponsors link * Add badge to readme
2020-12-16Add FAQ link to Issue template (#14020)6543
2020-11-18Config lock bot (#13624)6543
* config lock bot * Update .github/lock.yml
2020-10-21add more clarification to the issue-template.md (#13235)zeripath
Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2020-10-17Remove not relevant option from issue template (#13188)mrsdizzie
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.
2020-01-22Improve stale message (#9920)Antoine GIRARD
* Improve stale nessage * Update .github/stale.yml Co-authored-by: guillep2k <18600385+guillep2k@users.noreply.github.com>
2019-07-02Display Github support button (#7343)Antoine GIRARD
This need an option to be enabled on repo : https://help.github.com/en/articles/displaying-a-sponsor-button-in-your-repository
2019-03-08Add security note to issue template (#6281)John Olheiser
2019-01-19Force the PR close time to 60 days (#5770)Antoine GIRARD
Like the comment that is posted. Ex: https://github.com/go-gitea/gitea/pull/4749 is closed after 2 weeks and not 2 months
2018-12-20Create stale bot config (#5243)Antoine GIRARD
2017-08-09Comment help text for issues (#2281)Patrick G
2017-06-28Add link to forum in issue template (#2070)Jonas Östanbäck
2017-06-11Update links to Discord serverJonas Östanbäck
2017-03-10Add MSSQL to issues template (#1171)esell
2017-03-09Fix grammar (#1158)Patrick G
2017-02-17Add Screenshot-secion to IssueTemplate.md (#939)Kim "BKC" Carlbäcker
For `UI`-bugs we usually require a Screenshot to debug it :wink:
2016-12-31Replace pull request with issue at issue_template (#547)Bwko
2016-12-15Update example install url from try.gogs.io to try.gitea.io (#385)Sandro Santilli
* 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
2016-11-28Unified GitHub templates accross all projectsThomas Boerger
2016-11-05Review issue and pull templates, drop unused contributing fileSandro Santilli
The CONTRIBUTING.md from root dir will be used by github
2016-11-03Change import reference to match gitea instead of gogs (#37)Rémy Boulanouar
2016-08-05Replace gogs.io http links with https version (#3386)rugk
2016-08-05#3348 always use relative avatar link in the templateUnknwon
2016-07-28Minor fix for pull request template [CI SKIP]Unknwon
2016-07-28Update GitHub templatesUnknwon
2016-03-23Update localesUnknwon
2016-03-02ISSUE_TEMPLATE: suggestion to test at try.gogs.ioLubomir I. Ivanov
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.
2016-02-24Prepare to releaseUnknwon
2016-02-21Removed duplicate of paragraphBart
2016-02-17Add issue and pull request templateUnknwon