code.gitea.io/gitea@v1.21.7/.gitea/issue_template.md (about)

     1  <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue -->
     2  
     3  <!--
     4      1. Please speak English, this is the language all maintainers can speak and write.
     5      2. Please ask questions or configuration/deploy problems on our Discord
     6         server (https://discord.gg/gitea) or forum (https://discourse.gitea.io).
     7      3. Please take a moment to check that your issue doesn't already exist.
     8      4. Make sure it's not mentioned in the FAQ (https://docs.gitea.com/help/faq)
     9      5. Please give all relevant information below for bug reports, because
    10         incomplete details will be handled as an invalid report.
    11  -->
    12  
    13  - Gitea version (or commit ref):
    14  - Git version:
    15  - Operating system:
    16    <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package -->
    17    <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. --->
    18    <!-- If you are using a package or systemd tell us what distribution you are using -->
    19  - Database (use `[x]`):
    20    - [ ] PostgreSQL
    21    - [ ] MySQL
    22    - [ ] MSSQL
    23    - [ ] SQLite
    24  - Can you reproduce the bug at https://try.gitea.io:
    25    - [ ] Yes (provide example URL)
    26    - [ ] No
    27  - Log gist:
    28  <!-- It really is important to provide pertinent logs -->
    29  <!-- Please read https://docs.gitea.com/administration/logging-config#collecting-logs-for-help -->
    30  <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini -->
    31  
    32  ## Description
    33  <!-- If using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please
    34       disable the proxy/CDN fully and connect to gitea directly to confirm
    35       the issue still persists without those services. -->
    36  
    37  ...
    38  
    39  
    40  ## Screenshots
    41  
    42  <!-- **If this issue involves the Web Interface, please include a screenshot** -->