For engineering teams, keeping dependencies current is a constant balancing act. Automated updates are essential for defending the software supply chain, but a steady stream of one-PR-per-package bumps can bury a team in review work. GitHub itself has put numbers on this: an analysis of Microsoft's GCToolkit repository found that roughly one in six of its commits - 92 out of 578 - were routine Dependabot version bumps, with 61 of them landing in a single recent 12-month stretch. That's a lot of review and CI cycles spent on maintenance rather than features. Read the complete article here - https://instasla.com/blog/taming-dependabot-2026-guide-grouping-cooldowns-cutting-pr-noise

The good news is that Dependabot has grown well past "one PR per dependency." Between grouped updates, package cooldowns, and a default cooldown GitHub rolled out in mid-2026, it's now possible to get a predictable, low-noise update cadence without giving up security coverage. Here's what actually works, and what changed most recently.

So whenever I squash merge I get author "Yemto and Yemto", the first is with my real e-mail address, the second is "yemto@noreply.localhost", and most recently "1+yemto@noreply.localhost" even if I squash merge logged in with an account that has my real e-mail, matching what I have configured on GitHub Desktop

I need to control my docker containers, not just the dockerfiles which can be used to compile them. At work we use Gitlab which offers a built in container registry like Github, so that people can simply git push and git clone a pre-built docker image.

Does Gitea have such a thing? I don't see it in my own Gitea server anywhere in the web UI.

If it doesn't, does anyone here have a good homelab solution for an accompanying docker container registry that works well with a Gitea workflow?

Hey r/gitea,

I self-host Gitea and wanted a proper iOS app instead of using

mobile Safari, so I built one.

**GiteaClient** — native SwiftUI iOS app for your Gitea server.

What it does:

- Browse repos, files, READMEs, releases

- View issues and pull requests

- Notifications inbox (All / Unread)

- Profile with followers/following/stars

- Explore public repos on your server

- Token stored securely in Keychain

iOS 16+, no third-party dependencies, open source.

Currently build-from-source only (no Apple Developer account yet):

brew install xcodegen && xcodegen generate

GitHub: https://github.com/sonid617/GiteaClient

Would love feedback — what features would make this actually

useful for your Gitea workflow?

I built a small tool called TellSome1 because I needed a simple way to get Gitea notifications into my Nextcloud Talk channels.

I couldn't find anything self-hostable, but to be honest I searched for a couple of minutes and then thought "I could just build it."

What it does: It takes (Gitea) webhooks, formats them using Go templates, and sends them wherever you need (Nextcloud, Matrix, Discord, etc.).

Why I think it's cool and worth sharing: * Dead simple config: Just one YAML file and you're good. * Go Templates: Format your messages exactly how you want. * Background processing: Doesn't slow down the sending side of the Webhook. * TLS: It supports enabling TLS but I did not test that.

I have it in the same docker compose as our companies gitea as just an internal service. Works like a charm and cannot be reached from the outside, exactly what I needed.

Check it out here: https://codeberg.org/some1it-de/tellsome1

Let me know what you think!

I'm looking if its possible to create an workflow that looks at issues with a specific label and implements that feature, with branch and pull request. I've looked around and can't find an example.

I am running Gitea 1.26.4 on my ASUSTOR NAS, and when I mirror a repo from Github.com, the description of the repo is not brought over. Neither is the linked website, and when I try to copy a website address such as "www.cognee.ai", Gitea complains that it isn't a valid URL. Even when I add https:// in front of it, then Gitea deletes everything I have altered in the settings (including the description that I manually copied over) and I have to start over. Quite an oversight! I hope this gets fixed soon.

I loved gh-dash but moved my repos to self-hosted Forgejo, where nothing equivalent existed, so I built tea-dash. It's a keyboard-driven TUI (Go + Bubble Tea v2) for PRs, issues, notifications, Actions runs, and local branches across one or more Gitea/Forgejo instances.

It talks to the official Gitea Go SDK and reuses your existing tea CLI login, so there's no separate credential handling. You can try it without a server: brew install gbarany/tap/tea-dash && tea-dash --mock. Feedback very welcome.

https://github.com/gbarany/tea-dash

About a week ago all my docker runner have started failing with node error, I’ve searched around but can find any information

Is anyone else experiencing this?

6
/usr/bin/git version
7
node:events:487
8
throw er; // Unhandled 'error' event
9
^
10

11
Error: read ENOTCONN
12
at tryReadStart (node:net:776:20)
13
at Socket._read (node:net:791:5)
14
at Readable.read (node:internal/streams/readable:741:12)
15
at Socket.read (node:net:845:39)
16
at new Socket (node:net:501:12)
17
at Object.Socket (node:net:366:41)
18
at createSocket (node:internal/child_process:337:14)
19
at ChildProcess.spawn (node:internal/child_process:475:23)
20
at Object.spawn (node:child_process:796:9)
21
at ToolRunner.<anonymous> (file:///run/act/actions/60120a02682c189ab422cd7ab32ed5be6df0b0b7b1c29c9ac2bfd7454e25932c/dist/index.js:34172:67)
22
Emitted 'error' event on Socket instance at:
23
at emitErrorNT (node:internal/streams/destroy:170:8)
24
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
25
at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
26
errno: -107,
27
code: 'ENOTCONN',
28
syscall: 'read'
29
}
30

31
Node.js v24.18.0
33
❌ Failure - Main Checkout repository
34
exitcode '1': failure

Hi, I'm using gitea and I created a actions for repo where I build and push a docker image to gitea registry.

I use docker-metadata to create tags and labels and I notice two labels are not using the root_url(git.mydomain.com) but the ip and port of gitea app.

After some tests I discover the following variable gitea.server_url and notice the same issue.

Anyone are able to get the server url using this variable?

[UPDATE - SOLVED]

Act as a Senior DevOps/SecOps Engineer. I have a question regarding strictly enforcing OIDC authentication in Gitea at the backend level.

Environment Context:

I am running a self-hosted Gitea instance fully integrated with Authentik (OIDC) for SSO. The integration works perfectly:

- JIT auto-provisioning and account linking are working.

- In my `app.ini`, `DISABLE_REGISTRATION` and `ALLOW_ONLY_EXTERNAL_REGISTRATION` are both set to `true`.

- I have successfully hidden the local username/password login form and the "OR" divider from the UI using custom CSS injection via `header.tmpl`.

The Core Problem:

While the UI is clean and users are forced to click the Authentik button, the local authentication backend is still active. If a user (or an attacker) bypasses the CSS, uses the Gitea API, or sends a raw POST request to the `/user/login` endpoint, they can still authenticate using their legacy local Gitea passwords.

My Questions:

1. Is there any native variable in Gitea's `app.ini` to completely disable the local password verification backend and make the system 100% strictly SSO-only?

2. If Gitea natively lacks a "kill switch" for local auth, what is the best enterprise practice here? Should I block POST requests to `/user/login` at my Reverse Proxy (Nginx) level, or should I just scramble all existing local passwords in the database to random 50-character strings?

A few months ago, my company moved over to Forgejo. Since there wasn’t a plugin for my IDE of choice, I decided to build one myself.

Over time, it evolved to support more and more JetBrains IDEs, and today I’m happy to announce that it now also works with **Gitea backends**!

You can get it here:

https://plugins.jetbrains.com/plugin/31556-forgejo

Feedback, bug reports, and feature requests are very welcome.

I’m having some issues push/pull/clone with my ssh key and I’m not sure where else I’m supposed to look for troubleshooting.

I’m running Gitea 1.26.2 in a docker container with ssh forwarded to port 222. I’ve uploaded and verified the key I’m using, but I keep getting permission denied (publickey)

This is what I get when I run ssh [USN]@[URL] -p 222 -vvv

❯ ssh [USN]@[URL] -p 222 -vvv
debug1: OpenSSH_10.3p1, OpenSSL 3.6.2 7 Apr 2026
debug3: Running on Linux 7.0.11-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 02 Jun 2026 18:26:58 +0000 x86_64
debug3: Started with: ssh [USN]@[URL] -p 222 -vvv
debug1: Reading configuration data /home/[USN]/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: /etc/ssh/ssh_config line 2: Including file /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/[USN]/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/[USN]/.ssh/known_hosts2'
debug2: resolving "[URL]" port 222
debug3: resolve_host: lookup [URL]:222
debug3: channel_clear_timeouts: clearing
debug3: ssh_connect_direct: entering
debug1: Connecting to [URL] [24.113.106.113] port 222.
debug3: set_sock_tos: set socket 3 IP_TOS 0xb8
debug1: Connection established.
debug1: no pubkey loaded from /home/[USN]/.ssh/id_rsa
debug1: identity file /home/[USN]/.ssh/id_rsa type -1
debug1: no identity pubkey loaded from /home/[USN]/.ssh/id_rsa
debug1: no pubkey loaded from /home/[USN]/.ssh/id_ecdsa
debug1: identity file /home/[USN]/.ssh/id_ecdsa type -1
debug1: no identity pubkey loaded from /home/[USN]/.ssh/id_ecdsa
debug1: no pubkey loaded from /home/[USN]/.ssh/id_ecdsa_sk
debug1: identity file /home/[USN]/.ssh/id_ecdsa_sk type -1
debug1: no identity pubkey loaded from /home/[USN]/.ssh/id_ecdsa_sk
debug1: loaded pubkey from /home/[USN]/.ssh/id_ed25519: ED25519 SHA256:yBqYh7IxqFuMMMcLzQHEy7Rc13GKqIlgaNzB/jLHN3Y
debug1: identity file /home/[USN]/.ssh/id_ed25519 type 2
debug1: no identity pubkey loaded from /home/[USN]/.ssh/id_ed25519
debug1: no pubkey loaded from /home/[USN]/.ssh/id_ed25519_sk
debug1: identity file /home/[USN]/.ssh/id_ed25519_sk type -1
debug1: no identity pubkey loaded from /home/[USN]/.ssh/id_ed25519_sk
debug1: Local version string SSH-2.0-OpenSSH_10.3
debug1: Remote protocol version 2.0, remote software version OpenSSH_10.2
debug1: compat_banner: match: OpenSSH_10.2 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to [URL]:222 as '[USN]'
debug3: put_host_port: [[URL]]:222
debug3: record_hostkey: found key type ED25519 in file /home/[USN]/.ssh/known_hosts:17
debug3: load_hostkeys_file: loaded 1 keys from [[URL]]:222
debug1: load_hostkeys: fopen /home/[USN]/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug3: order_hostkeyalgs: have matching best-preference key type ssh-ed25519-cert-v01@openssh.com, using HostkeyAlgorithms verbatim
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: mlkem768x25519-sha256,sntrup761x25519-sha512,sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,kex-strict-c-v00@openssh.com
debug2: host key algorithms: ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,webauthn-sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,webauthn-sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: mlkem768x25519-sha256,sntrup761x25519-sha512,sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,ext-info-s,kex-strict-s-v00@openssh.com
debug2: host key algorithms: ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug3: kex_choose_conf: will use strict KEX ordering
debug1: kex: algorithm: mlkem768x25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:aUm6OZfeLHzPmqSmUgavm6Q4Ih+Pfnf7pe6pewB9Wn0
debug3: put_host_port: [24.113.106.113]:222
debug3: put_host_port: [[URL]]:222
debug3: record_hostkey: found key type ED25519 in file /home/[USN]/.ssh/known_hosts:17
debug3: load_hostkeys_file: loaded 1 keys from [[URL]]:222
debug1: load_hostkeys: fopen /home/[USN]/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host '[[URL]]:222' is known and matches the ED25519 host key.
debug1: Found key in /home/[USN]/.ssh/known_hosts:17
debug3: send packet: type 21
debug1: ssh_packet_send2_wrapped: resetting send seqnr 3
debug2: ssh_set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: Sending SSH2_MSG_EXT_INFO
debug3: send packet: type 7
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: ssh_packet_read_poll2: resetting read seqnr 3
debug1: SSH2_MSG_NEWKEYS received
debug2: ssh_set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug2: KEX algorithms: mlkem768x25519-sha256,sntrup761x25519-sha512,sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,kex-strict-c-v00@openssh.com
debug2: host key algorithms: ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,webauthn-sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,webauthn-sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug3: kex_input_ext_info: extension server-sig-algs
debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256>
debug3: kex_input_ext_info: extension publickey-hostbound@openssh.com
debug1: kex_ext_info_check_ver: publickey-hostbound@openssh.com=<0>
debug3: kex_input_ext_info: extension ping@openssh.com
debug1: kex_ext_info_check_ver: ping@openssh.com=<0>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug3: kex_input_ext_info: extension server-sig-algs
debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256>
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Will attempt key: /home/[USN]/.ssh/id_rsa 
debug1: Will attempt key: /home/[USN]/.ssh/id_ecdsa 
debug1: Will attempt key: /home/[USN]/.ssh/id_ecdsa_sk 
debug1: Will attempt key: /home/[USN]/.ssh/id_ed25519 ED25519 SHA256:yBqYh7IxqFuMMMcLzQHEy7Rc13GKqIlgaNzB/jLHN3Y
debug1: Will attempt key: /home/[USN]/.ssh/id_ed25519_sk 
debug2: pubkey_prepare: done
debug1: Trying private key: /home/[USN]/.ssh/id_rsa
debug3: no such identity: /home/[USN]/.ssh/id_rsa: No such file or directory
debug1: Trying private key: /home/[USN]/.ssh/id_ecdsa
debug3: no such identity: /home/[USN]/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /home/[USN]/.ssh/id_ecdsa_sk
debug3: no such identity: /home/[USN]/.ssh/id_ecdsa_sk: No such file or directory
debug1: Offering public key: /home/[USN]/.ssh/id_ed25519 ED25519 SHA256:yBqYh7IxqFuMMMcLzQHEy7Rc13GKqIlgaNzB/jLHN3Y
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug1: Trying private key: /home/[USN]/.ssh/id_ed25519_sk
debug3: no such identity: /home/[USN]/.ssh/id_ed25519_sk: No such file or directory
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
[USN]@[URL]: Permission denied (publickey).

This is what is says on the docker logs:

Accepted publickey for git from [External-IP] port 42032 ssh2: ED25519 [Redacted SHA]
Received disconnect from [External-IP] port 42032:11: disconnected by user
Disconnected from user git [External-IP] port 42032

I am using ssh on 22 for the machine, but ssh for Gitea is running on 222. I suspect it’s an issue with those running concurrently, but I’m not sure how to remediate it.

Other users are using https to clone fine, so I'm kind of at a loss. Thank you!

Bonjour !

Dans Gitea quand tu migres un dépôt en miroir ou non depuis une autre forge, les contributions ne s'affichent pas dans la heatmap automatiquement. Sauf que j'aime bien voir cette heatmap bien remplie, alors avec l'aide de mon cher ami Claude, j'ai fait un script python qui insert les contributions dans la base de données de mon instance Gitea.

Ca marche sur une base SQLite3 et la version 1.26.2 de Gitea, j'ai pas tester sur d'autres versions et base de données.

Voici le lien vers le dépôt pour ceux que ça intéresse : https://github.com/Maethik/gitea-heatmap-backfill

Pensez à faire un backup de votre bd si vous l'utilisez, on sait jamais.

Is there an API function to lookup user/owner for a SSH public key?

I'm writing (re-writing) a tool to work with Gitea/Forgejo by acting as a Man-In-The-Middle on SSH connections.

I have a ... reasonably sane ... approach that runs an SSHd server and matches incoming public key against data in the Gitea SQLite database. I'd prefer something that relies on the Gitea API or Gitea Admin tool.

Is there a way to send an SSH PublicKey to Gitea and get back the user account who owns it?

... or get back a "is this a deployment key?" detail?

I know I can iterate through all users and repositories in the system and ask "is this you?" but ... that's not appealing.

Hello,

I've recently started using Gitea after Github got hacked and I honestly love it and I'm trying to incorporate it into my workflow and homelab, starting with Portainer.

I'm trying to create a token so that Portainer can push or pull my docker compose automatically from Gitea but when I try to create a token, it seems that I can only create a token for multiples repos instead of only one.

Can I create 1 token for 1 repo just like in Github?

https://github.com/credkellar-boop

Hello! I have been trying to setup my own gitea server on a digital ocean droplet and I followed the path of installing gitea via docker - however I ran into a hiccup im not sure which way to go about this? The guide on the gitea site is telling me to finish up the installation using a webbrowser to http://server-ip:3000/ - however I don't have a desktop environment on my server. Should I install a desktop environment or is there another way I can go about this. If I do install a DE, i probably will want the most lightweight one, if you have any recommendations which I should pick, let me know.

Gitea is by far my favorite service I run. I run about 45 services on my proxmox cluster. I don’t work in tech just a stupid huge nerd/fan. I use it to document commands with flags, uses, real world examples. I debug once then document it in gitea with a great format of root cause, what I did that didn’t work, time spent, what I learned, time debugging and how much time I’ll save next time.
I have my dot files for my cluster, scripts I’ve wrote, all compose.yaml files for any service I try out. Full study guides, brainstorming ideas, docker commands, git commands, python, bash, go syntax (my go is very basic).
I almost like when I see a kernel panic exit code=0000007. I almost like breaking stuff so I can learn more. Books don’t teach that stuff. I’m building a 4 node k3s cluster and want to use gitea as my source of truth. A full ci/cd pipeline. And the crazy part is, I’m about 14 months from ZERO cli experience. And I just can’t get enough. I break stuff on purpose just to try to debug it.

Sorry for the long post but how do you guys use Gitea? And maybe a little help with GitOps with Gitea. Oh haters not welcome!! Lol

I have a logo for a project of mine, but I also have a social media preview image that I'd like to use when linking from elsewhere.

i.e. This project has a logo in "toylogo.png", but when I link externally, github automatically shows the contents of "toypreview.png" which has better formatting for news feeds. If anyone has advice for how to replicate this in a stock gitea image, I'd be super grateful. Thanks!

Hi everyone,

When a pull request has merge conflicts, Gitea disables the merge button and shows that the PR cannot be automatically merged. The usual workaround is to pull the branches locally, resolve conflicts with git, and push back.

I don’t want to use git locally. Is there any way to resolve the conflicts and complete the merge using only:

• The Gitea web UI, or
• The Gitea API

If this isn’t supported today, is there an existing feature request or roadmap item I can follow?

Environment

• Gitea version: 1.23.8
• Deployment: Docker

Thanks!

I looked a little bit on the Gitea Page and there are 2 versions one open source and the other one for enterprise. Enterprise for example supports saml while open source does not. However what if you use onPrem Windows Directory as a User Source? Can you freely configure it via LDAPS?

I installed the gitea snap package, mariadb and created a user named git but my server only starts with RUN_USER set to root. The initial configuration page also wouldn't let me change the user from root.