Mismatched instructions for SSH/HTTPs #7525

Closed
opened 2025-11-02 07:28:41 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @adyanth on GitHub (Jun 29, 2021).

  • Gitea version (or commit ref): 1.15.0+dev-494-g35f37a362 built with GNU Make 4.3, go1.16.5 : bindata, timetzdata, sqlite, sqlite_unlock_notify
  • Git version: 2.30.2
  • Operating system: Ubuntu-20.04 Docker install
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
  • Log gist:

Description

See below. The instructions don't match the protocol selected after creating a repo, and on every reload.

Screenshots

After creating a repo
image

2nd repo
image

Switch to SSH
image

Switch back to HTTPS
image

Reload page
image

This is inconsistent behavior as one would expect the instructions to align with the selected scheme.

Originally created by @adyanth on GitHub (Jun 29, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. 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.15.0+dev-494-g35f37a362 built with GNU Make 4.3, go1.16.5 : bindata, timetzdata, sqlite, sqlite_unlock_notify - Git version: 2.30.2 - Operating system: Ubuntu-20.04 Docker install <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [X] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [X] Yes (provide example URL): https://try.gitea.io/adyanth/test - [ ] No - Log gist: <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description <!-- If using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please disable the proxy/CDN fully and connect to gitea directly to confirm the issue still persists without those services. --> See below. The instructions don't match the protocol selected after creating a repo, and on every reload. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> After creating a repo ![image](https://user-images.githubusercontent.com/33192449/123790753-5424fb00-d8fc-11eb-992a-ae6d9e11b7a5.png) 2nd repo ![image](https://user-images.githubusercontent.com/33192449/123790835-6868f800-d8fc-11eb-910a-822cf5d1244b.png) Switch to SSH ![image](https://user-images.githubusercontent.com/33192449/123790882-73238d00-d8fc-11eb-9fce-4665ed10422e.png) Switch back to HTTPS ![image](https://user-images.githubusercontent.com/33192449/123790939-82a2d600-d8fc-11eb-8eed-5ae611cb235b.png) Reload page ![image](https://user-images.githubusercontent.com/33192449/123791186-c39aea80-d8fc-11eb-939f-dc929b4793bc.png) This is inconsistent behavior as one would expect the instructions to align with the selected scheme.
GiteaMirror added the topic/uitopic/build labels 2025-11-02 07:28:41 -06:00
Author
Owner

@6543 commented on GitHub (Jun 29, 2021):

note: if you klick to ssh and back to https, it get changed to a valid https commands ...

@6543 commented on GitHub (Jun 29, 2021): note: if you klick to ssh and back to https, it get changed to a valid https commands ...
Author
Owner

@adyanth commented on GitHub (Jun 29, 2021):

Yes, also provided screenshots for the same.
Meaning it can show https commands, but won't do by default.

@adyanth commented on GitHub (Jun 29, 2021): Yes, also provided screenshots for the same. Meaning it can show https commands, but won't do by default.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7525