| 7 Mar 2024 |
 raitobezarius | In reply to @adam:robins.wtf
No why? | 23:58:12 |
 adamcstephens | I’m sure they’d find some explanation or just ignore it | 23:58:35 |
| raitobezarius | Ah yes but then what you are saying is that you already concluded they are of bad faith and clearly planning to just pull the rug | 23:58:56 |
| 8 Mar 2024 |
| adamcstephens | Yeah probably a bit, based on the moves since the soft fork what forgejo has said about them. I’d be happy to be wrong and see gitea do amazing things. Unfortunately, I’d argue there’s enough examples in the past to suggest things won’t turn back toward community. | 00:01:43 |
| adamcstephens | * Yeah probably a bit, based on the moves since the soft fork and what forgejo has said about them. I’d be happy to be wrong and see gitea do amazing things. Unfortunately, I’d argue there’s enough examples in the past to suggest things won’t turn back toward community. | 00:07:21 |
 hexa | In reply to @raitobezarius:matrix.org
what if I send SAML support to Gitea tomorrow? looks for a simpler feature and doit 😄 | 00:15:40 |
| hexa | In reply to @raitobezarius:matrix.org
what if I send SAML support to Gitea tomorrow? * looks for a simpler feature and do it 😄 | 00:15:44 |
| hexa |
IP Allowlist: Control access to your repositories by specifying approved IP addresses.
| 00:16:03 |
| hexa | that sounds equally silly and simple | 00:16:08 |
| raitobezarius | https://github.com/go-gitea/gitea/pull/29403 I have a better answer | 16:46:49 |
| raitobezarius | Yes and it's the one used in Gitea Enterprise | 16:46:57 |
| hexa |
Yes, CommitGo is using this PR.
| 16:50:12 |
