WISH: One try.gitea.io for devel (as now) and one for the stable release #2882

Open
opened 2025-11-02 04:52:33 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @HenrikBengtsson on GitHub (Feb 9, 2019).

  • Gitea version (or commit ref): 1.7.1 and devel (c3d8fb7)
  • Git version: N/A
  • Operating system: N/A (browser)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

While trying to troubleshoot an issue occurring with Gitea 1.7.1, I went to https://try.gitea.io/ currently using Gitea devel (commit c3d8fb7) to discover the issue does not occur there. However, looking at the commit history, I don't see anything obvious that would have resolved this issue, which means that the problem might be with my installation.

For troubleshooting purposes, for improved bug report examples, and to lower the number of false-positive bug reports, I'd like to suggest the option for running https://try.gitea.io/ with either the most recent release and the most recent devel commit.

Just a thought ...

PS. The problem observed is that when on mobile browsers only and searching issues by labels (e.g. click on a label), I will loose the label filter when I click 'Next' page (or any of the numbered pages). For example, when searching something like https://try.gitea.io/HenrikBengtsson/test/issues?q=&type=all&state=open&labels=3005&milestone=0&assignee=0, clicking next will set ...&labels=&.... Again, this only occurs with my local Gitea 1.7.1 instance but not with try.gitea.io (and not on the desktop). Don't worry about this - I'll keep an eye out for it when the next version is released.

Screenshots

Originally created by @HenrikBengtsson on GitHub (Feb 9, 2019). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.7.1 and devel (c3d8fb7) - Git version: N/A - Operating system: N/A (browser) - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description While trying to troubleshoot an issue occurring with Gitea 1.7.1, I went to https://try.gitea.io/ currently using Gitea devel (commit c3d8fb7) to discover the issue does not occur there. However, looking at the commit history, I don't see anything obvious that would have resolved this issue, which means that the problem might be with my installation. For troubleshooting purposes, for improved bug report examples, and to lower the number of false-positive bug reports, I'd like to suggest the option for running https://try.gitea.io/ with either the most recent release and the most recent devel commit. Just a thought ... PS. The problem observed is that when on *mobile* browsers only and searching issues by labels (e.g. click on a label), I will loose the label filter when I click 'Next' page (or any of the numbered pages). For example, when searching something like <https://try.gitea.io/HenrikBengtsson/test/issues?q=&type=all&state=open&labels=3005&milestone=0&assignee=0>, clicking next will set `...&labels=&...`. Again, this only occurs with my local Gitea 1.7.1 instance but not with try.gitea.io (and not on the desktop). Don't worry about this - I'll keep an eye out for it when the next version is released. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/proposal label 2025-11-02 04:52:33 -06:00
Author
Owner

@lunny commented on GitHub (Feb 9, 2019):

https://try.gitea.io will always follow master version.

@lunny commented on GitHub (Feb 9, 2019): https://try.gitea.io will always follow master version.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2882