Gitea / is on Nostr

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD

Last Notes

2025-04-04 16:58:55

- reply

@nprofile…4qc7 @nprofile…qe73
You’re free to use a self-hosted LLM, especially since many lightweight models can now run locally. The choice of which LLM to use and what training data to include is entirely up to you. This is independent of any web crawler usage.

2025-04-03 22:18:38

- reply

@nprofile…prfl This is a standalone open source project that implements MCP for any Gitea instance. Its use is completely optional.
Please note that the quality of the generated code depends on both the large language model (LLM) used and the quality of the prompts provided.

2025-04-03 21:13:15

- reply

@nprofile…qqx9 you don’t need to. This isn’t included in Gitea, but a separate thing.

2025-04-03 18:35:25

🚀 Introducing Gitea MCP Server 🚀
We’re excited to announce the release of the Gitea MCP Server. A New Paradigm for AI-Driven Code Collaboration. https://about.gitea.com/resources/tutorials/gitea-mcp-server
https://sb-gitea.b-cdn.net/media_attachments/files/114/275/471/932/872/372/original/eb3d1a7889dd06dd.png

2025-02-20 00:38:54

We are excited to announce that Gitea 1.23.4 has been released!
This update patches security issues, so we recommend upgrading immediately to keep your instance secure.
Read more about all the changes: https://blog.gitea.com/release-of-1.23.4/

2025-02-20 00:38:54

2024-12-01 22:17:04

- reply

@nprofile…7cpf it’s being worked on :)

2024-12-01 22:17:04

- reply

@nprofile…7cpf it’s being worked on :)

2024-11-24 17:44:58

- reply

@nprofile…g6ue @nprofile…gxmg @nprofile…f3qs that domain resolves to an “internal IP” due to going through a proxy, and by default those are disabled to prevent “SSRF” attacks. You can enable local domains through the configuration options listed in the error message

2024-11-24 17:44:58

- reply

2024-11-08 15:56:52

- reply

@npub1ked…62j2 Good news! There is a current work-around, where you have an "ignite" runner that your repo has a trigger workflow for, and when jobs come in, the ignite is always running and will wakeup/create your actual runner for incoming tasks, and then we just merged "one-shot" capabilities for the runner so that when the job is complete the runner will stop and your machine can go back to sleep.
We are working on additional functionality so that this ignite runner isn't needed :)

2024-11-08 15:56:52

- reply