9 ms·

Gitea 1.19

167 points by silverwind 4y ago

fariszr 4y ago
They've done it, Open source GitHub Actions! I hope politics don't get in the way of Codeberg adopting actions, as they are very involved in the woodpecker project. Looking forward to testing it with few actions, docker-buildx and my docker-compose-gitops-action, https://github.com/FarisZR/docker-compose-gitops-action https://github.com/FarisZR/docker-compose-gitops-action edit: looks like Forgejo is already talking about Actions support https://forgejo.org/2023-02-27-forgejo-actions/ https://forgejo.org/2023-02-27-forgejo-actions/
fullstop 4y ago
Since the link doesn't really tell you what it is, this is a self hosted Git service written in Go. It looks a lot like GitHub.
cacois 4y ago
I've used gitea for years in my homelab - so far great for my non-exterprise needs.
candiddevmike 4y ago
Really excited for Gitea Actions!! Will probably look into switching from GitHub now. Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system.
- KronisLV 4y ago
  > Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system. I'm in the opposite camp, especially when this separate system is as simple as Drone CI or Woodpecker CI (I mostly use the former, but the latter is more permissive, license wise). I came to holding this view after I ran into some issues by using a self-hosted GitLab Omnibus install previously: https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-nexus-and-drone https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-... Using separate systems for working with the code, doing CI/CD and storing artifacts made each of the parts easier to update, limit the resources available to each, as well as limited the fallout when something does go wrong - say, still being able to interact with the codebase, even if the container repo is temporarily unavailable, or vice versa. That said, in a few years I might come around to holding the opposite views again - frankly, both approaches are good and seeing the Gitea Actions project is nice! Though I'll also acknowledge that some might claim that all-in-one solutions are sometimes a bit half-baked, a criticism that I've heard of GitLab in the past (though honestly they're also fine, especially for the more enterprise settings, where you have beefier servers and a few people to manage the install).
  - fjni 4y ago
    I'm with you on this. I would expand this further yet and say that introducing this as a feature creates a whole set of security concerns that just weren't there before.
  - potamic 4y ago
    Concur. Composability, separation of concerns, do one thing and one thing well, etc. are all philosophies as old as time in this industry. Any programmer worth their salt would understand the value they provide. Source code hosting has nothing to do with building your software and it's a bad idea to mix them up. This situation is actually a bit more insidious. All these CI/CD features are just a thinly veiled attempt at locking users into the platform. There's not big money to be made selling git hosting, but if you control how the software is built, then you have made yourself a hard dependency. If you look at the starter workflows they provide, they encourage bad practices where your application build is defined in their DSL. Experienced programmers might steer away from such usage, but many novice won't. If you have enough novice adoption, it becomes the norm. So many projects these days cannot even be built locally without a CI service dependency, where instead 99% of the time, all you needed was a simple makefile.
- jamesu 4y ago
  Gitea actions looks neat though I'm not sure how you are meant to run windows or mac-centric workflows with it since the runtime (nektos/act) seems to require docker. If its not possible that might limit its usefulness somewhat...
  - aorth 4y ago
    > docker Alternatively, I was wondering if it supported podman. I prefer podman in most cases since it runs without root and doesn't mess with my host's nftables. Docker always invokes iptables and adds a bunch of chains/rules. Grrr...
  - techknowlogick 4y ago
    One contributor to nektos/act and Gitea's act_runner (ChristopherHX) contributor "host" mode to act, which allows you to run without docker. Disclaimer: I am a part of the Gitea project, the TOC, and am employed to work on Gitea
    - candiddevmike 4y ago
      I think this is the PR: https://github.com/nektos/act/pull/1293 https://github.com/nektos/act/pull/1293 This is perfect for my needs. Thank you to the Gitea folks for getting this added/integrated!
- hdjjhhvvhga 4y ago
  Don't do it yet otherwise you will fill disappointed by teething problems. Do it in 3 months and then - if they keep the current dynamics - you will be able to work with GA more comfortably and only encounter minor bugs.
- geek_at 4y ago
  It's mindblowing for me how many of the features I love from github are now in gitea. Actions, email replies, scoped lables, fine-tunable access tokens, secrets and also the ability to push local git repos to gitea without having to create them via the web interface first.
bioemerl 4y ago
[flagged]
- rhaway84773 4y ago
  That’s a pretty strong statement to make without backing it up with some evidence of foul play, or at least evidence of these links.
  - supriyo-biswas 4y ago
    Also Chinese author != CCP. You can read the source code and build binaries from the provided source.
    - bioemerl 4y ago
      With a large project unless a large auditor goes into your code and reads it with a fine comb it's not a good idea to have blind trust in it. And Chinese author does mean CCP, assuming they live in China they are almost certainly able to be compromised and it is a bad decision to trust them with something as valuable as your whole code base.
  - bioemerl 4y ago
    If you have evidence of foul play it's already far far too late to do anything. With authoritarian nations and their ability to control and steal your projects, you assume guilty until proven innocent. You should require there be a real audit before you trust gitea.
    - 5e92cb50239222b 4y ago
      Half of gitea's contributors are from Europe. Wait until you learn how much "Chinese" code is in the Linux kernel these days. This anti-Chinese hysteria is hilarious to watch from the sidelines, honestly. A few months ago there was a comment on HN by some American whose company was rewriting their frontend when they learned that antd (a React component toolkit) was developed by a Chinese company. https://github.com/ant-design/ant-design https://github.com/ant-design/ant-design
barnabee 4y ago
For info: there was some drama a while back [0], [1] and some (a lot?) of the community/devs went to https://forgejo.org/ https://forgejo.org/ Seemed to me like they had a point and it's worth considering following that project [2] instead. [0] https://gitea-open-letter.coding.social/ https://gitea-open-letter.coding.social/ [1] https://news.ycombinator.com/item?id=33372471 https://news.ycombinator.com/item?id=33372471 [2] https://codeberg.org/forgejo/forgejo https://codeberg.org/forgejo/forgejo
- candiddevmike 4y ago
  Will be interesting to compare the velocity between the two. Can a community fork keep pace and possibly even innovate more than the commercial upstream? There have been a few cases of open source collectives/coops that do what Gitea does but distribute the profits to contributors equally, wonder if any of those have reached sustainability.
- gempir 4y ago
  The issue is Forgejo doesn't really have the know-how or capabilities to drive this project forward. In the past months all they have done is rebrand Gitea and some minor fixes, but upstream (gitea) has added a huge number of features and merged tons of valuable pull requests. So are they just going to continuously merge upstream into their fork and do nothing besides that? The platform, Codeberg might be "well" funded but not to maintain another extra project and develop new features for it. I think the outrage was a little too big initially. It's a big task to create a git host that needs to compete with Github and the likes and I think it's fair that you want to make some money on the side with that. Compare these merged PRs: Forgejo https://codeberg.org/forgejo/forgejo/pulls?q=&type=all&sort=recentupdate&state=closed&labels=&milestone=0&assignee=0&poster=0 https://codeberg.org/forgejo/forgejo/pulls?q=&type=all&sort=... Gitea https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclosed+sort%3Aupdated-desc https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclose...
  - tjoff 4y ago
    > I think the outrage was a little too big initially. It's a big task to create a git host that needs to compete with Github and the likes and I think it's fair that you want to make some money on the side with that. That seems completely irrelevant and orthogonal to the outrage though?
warent 4y ago
very excited about Actions. For several months I've been using a home server Gitea for a Unity project version control, because the project size is far too large for github/gitlab etc. So far everything about it has been excellent, and it's only getting better!
- techknowlogick 4y ago
  That's an awesome use-case! Are you using LFS in Gitea too with Unity? Are you working on anything publicly available? I'm looking for something new to play :) Disclaimer: I am a part of the Gitea TOC, and am employed to work on Gitea.
Kelamir 4y ago
As a novice at self-hosting, I previously attempted to use it, but got stuck as I didn't understand MySQL, and learning it just for Gitea was too much. However, I've had some progress with with another database recently, so I would like to give Gitea another try soon.
- dual_dingo 4y ago
  For small personal deployments, using SQLite as a database is usually sufficient. This means you don't need a fullblown SQL server, instead the whole database consists of a single file.
  - geek_at 4y ago
    can confirm have about 20 repos and 1 org in my gitea and I never have problems with loading speeds
dave78 4y ago
What are the current thoughts on Gitea vs Forgejo? I'm thinking of migrating from a self-hosted Gitlab to one of them in the near future. The way Gitea was taken over leaves a bad taste in my mouth so I'm leaning towards Forgejo, but it's not really clear to me if that's the right choice.
- CameronNemo 4y ago
  I am personally not a fan of Forgejo relicensing (to AGPL). Makes the "soft fork" aspect so much harder, because anything contributed to Forgejo cannot be easily cherry picked onto Gitea.
- jpace121 4y ago
  Forgejo currently is only applying branding changes and currently plans on being a soft fork. I think it’s existence is a good thing for the ecosystem (if Gitea the Company did something wonky, there will be an organized group already doing releases ready to go), but I’m not sure there is a huge benefit in running it, at this juncture.
  - dave78 4y ago
    The other discussion in this thread has convinced me that for now, the momentum seems to be with Gitea, so I'll probably lean towards that. I'm still disappointed in how the whole situation was handled, though, and it leaves me wondering what other changes will be around the corner.
justin_oaks 4y ago
I remember there being a big stink about Gitea, so much so that it was forked: https://news.ycombinator.com/item?id=34011581 https://news.ycombinator.com/item?id=34011581 I don't use Gitea, but if I were to start today would there be a proper reason to avoid Gitea?
- Macha 4y ago
  Gitea was taken from a community run project to an corporate owned one to allow for an open core future. Currently there's been no actions taken that negatively affect the open project, but the door is now open for a "This isn't working for our company, we're now going to SSPL" style move in the future.
  - jolheiser 4y ago
    I am a community member of the Gitea TOC, and there will be no open core model. Gitea will remain fully open source with no tiers. The community TOC also has advantages in any such voting where something may negatively affect the OS project, although as you mentioned that hasn't happened yet, and I don't expect it will.
- djha-skin 4y ago
  https://news.ycombinator.com/item?id=35233168 https://news.ycombinator.com/item?id=35233168
- jolheiser 4y ago
  Currently the fork is simple rebranding with a few small changes here and there. Both of them will give you nearly the same experience, and they are a soft fork so all Gitea changes will be available. I'm biased as a community member of the Gitea TOC, so I'd of course recommend Gitea.
djha-skin 4y ago
I'm super excited Gitea is becoming better and better. Gotta be honest though; the really exciting feature I'm waiting for is ActivityPub[1] support. That will really make my single gitea instance much more interesting, when I can accept PRs from other instances and make them to theirs. A lot of comments about "Forgejo". In short: meh. Not a big deal[2]. I'll be sticking with Gitea. 1: https://github.com/go-gitea/gitea/issues/14186 https://github.com/go-gitea/gitea/issues/14186 2: https://news.ycombinator.com/item?id=35233168 https://news.ycombinator.com/item?id=35233168
- lagniappe 4y ago
  is it for-guh-joe or for-jeh-ho?
  - jolheiser 4y ago
    I am not with the fork, but seeing as people ask this about us all the time I can relate. https://forgejo.org/static/forgejo.mp4 https://forgejo.org/static/forgejo.mp4
    - lagniappe 4y ago
      Is there ever internal discussion about the name?
sph 4y ago
Why is gitea, a self-hosted Github competitor, hosting its source on Github? Not a lot of dog-fooding going on over there.
- jolheiser 4y ago
  We are actively working on it, everything other than the main repo is on gitea.com and a lot of that is also being converted to dogfood actions. The main repo, however, has a lot of issues/prs/etc metadata and so migrating is a bit harder.
- xx_ns 4y ago
  They've been meaning to migrate for a while now, but have had various blockers. https://github.com/go-gitea/gitea/issues/1029 https://github.com/go-gitea/gitea/issues/1029
vorpalhex 4y ago
Ahhh this removes reverse proxy auth for the api! This is horrible! While reverse proxy auth should be disabled by default, this is critical. This breaking change makes gitea unsuitable for me going forward. Reverse proxy auth is perfectly secure when correctly setup and is sensible in many configurations.
- joencott 4y ago
  Not enough people are talking about this, as soon as the company took over they started to remove functionality. Shame on them.
  - jolheiser 4y ago
    This was not a company decision, it was proposed by a non-company member and approved by two other non-company members (and one company member, but just pointing out context).
- remram 4y ago
  It seems it was only removed from the API. Are you really using it there? Can you say more about your use case?
legends2k 4y ago
Nice to see Blender team being thanked as major contributors for Gitea :)
- techknowlogick 4y ago
  The Blender Foundation has been wonderful! Among their many PRs to this release, one of the big ones was scoped labels.
frodowtf 4y ago
Wow. Great progress! Recently, I was wondering why gitea does not have a GitHub Actions alternative. What a timing. BTW, a colleague of mine told me that GitHub Actions wasn't supposed to be a CI/CD alternative at the time when it was released. I couldn't find any note on that online. Is it true?
- Reitet00 4y ago
  FWIW it's possible to use Woodpecker as an alternative to Actions. I guess Gitea Actions will be more tightly coupled with Gitea.
  - techknowlogick 4y ago
    I was just telling someone else how great Woodpecker is. The protocol that Actions runners use to report logs/job statuses back to Gitea is an open protocol that maybe one day woodpecker could use it for enhanced integration with Gitea, so you could use woodpecker but have the experience be next to your code. Disclaimer: I am listed as a maintainer of Woodpecker. I am a also part of the Gitea TOC, and am employed to work on Gitea
- thiht 4y ago
  > GitHub Actions wasn't supposed to be a CI/CD alternative at the time when it was released Not sure what you mean by that, what was it supposed to be then?
Reitet00 4y ago
Wow, what a great changelog. I wish more software projects would take time to present their work to users like that.

167 points by silverwind 4y ago

They've done it, Open source GitHub Actions! I hope politics don't get in the way of Codeberg adopting actions, as they are very involved in the woodpecker project. Looking forward to testing it with few actions, docker-buildx and my docker-compose-gitops-action, https://github.com/FarisZR/docker-compose-gitops-action https://github.com/FarisZR/docker-compose-gitops-action edit: looks like Forgejo is already talking about Actions support https://forgejo.org/2023-02-27-forgejo-actions/ https://forgejo.org/2023-02-27-forgejo-actions/

fullstop 4y ago

Since the link doesn't really tell you what it is, this is a self hosted Git service written in Go. It looks a lot like GitHub.

cacois 4y ago

I've used gitea for years in my homelab - so far great for my non-exterprise needs.

candiddevmike 4y ago

Really excited for Gitea Actions!! Will probably look into switching from GitHub now. Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system.

KronisLV 4y ago
> Wasn't a fan of drone or having to maintain the integration with a separate CI/CD system. I'm in the opposite camp, especially when this separate system is as simple as Drone CI or Woodpecker CI (I mostly use the former, but the latter is more permissive, license wise). I came to holding this view after I ran into some issues by using a self-hosted GitLab Omnibus install previously: https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-nexus-and-drone https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-... Using separate systems for working with the code, doing CI/CD and storing artifacts made each of the parts easier to update, limit the resources available to each, as well as limited the fallout when something does go wrong - say, still being able to interact with the codebase, even if the container repo is temporarily unavailable, or vice versa. That said, in a few years I might come around to holding the opposite views again - frankly, both approaches are good and seeing the Gitea Actions project is nice! Though I'll also acknowledge that some might claim that all-in-one solutions are sometimes a bit half-baked, a criticism that I've heard of GitLab in the past (though honestly they're also fine, especially for the more enterprise settings, where you have beefier servers and a few people to manage the install).
- fjni 4y ago
  I'm with you on this. I would expand this further yet and say that introducing this as a feature creates a whole set of security concerns that just weren't there before.
- potamic 4y ago
  Concur. Composability, separation of concerns, do one thing and one thing well, etc. are all philosophies as old as time in this industry. Any programmer worth their salt would understand the value they provide. Source code hosting has nothing to do with building your software and it's a bad idea to mix them up. This situation is actually a bit more insidious. All these CI/CD features are just a thinly veiled attempt at locking users into the platform. There's not big money to be made selling git hosting, but if you control how the software is built, then you have made yourself a hard dependency. If you look at the starter workflows they provide, they encourage bad practices where your application build is defined in their DSL. Experienced programmers might steer away from such usage, but many novice won't. If you have enough novice adoption, it becomes the norm. So many projects these days cannot even be built locally without a CI service dependency, where instead 99% of the time, all you needed was a simple makefile.
jamesu 4y ago
Gitea actions looks neat though I'm not sure how you are meant to run windows or mac-centric workflows with it since the runtime (nektos/act) seems to require docker. If its not possible that might limit its usefulness somewhat...
- aorth 4y ago
  > docker Alternatively, I was wondering if it supported podman. I prefer podman in most cases since it runs without root and doesn't mess with my host's nftables. Docker always invokes iptables and adds a bunch of chains/rules. Grrr...
- techknowlogick 4y ago
  One contributor to nektos/act and Gitea's act_runner (ChristopherHX) contributor "host" mode to act, which allows you to run without docker. Disclaimer: I am a part of the Gitea project, the TOC, and am employed to work on Gitea
  - candiddevmike 4y ago
    I think this is the PR: https://github.com/nektos/act/pull/1293 https://github.com/nektos/act/pull/1293 This is perfect for my needs. Thank you to the Gitea folks for getting this added/integrated!
hdjjhhvvhga 4y ago
Don't do it yet otherwise you will fill disappointed by teething problems. Do it in 3 months and then - if they keep the current dynamics - you will be able to work with GA more comfortably and only encounter minor bugs.
geek_at 4y ago
It's mindblowing for me how many of the features I love from github are now in gitea. Actions, email replies, scoped lables, fine-tunable access tokens, secrets and also the ability to push local git repos to gitea without having to create them via the web interface first.

bioemerl 4y ago

[flagged]

rhaway84773 4y ago
That’s a pretty strong statement to make without backing it up with some evidence of foul play, or at least evidence of these links.
- supriyo-biswas 4y ago
  Also Chinese author != CCP. You can read the source code and build binaries from the provided source.
  - bioemerl 4y ago
    With a large project unless a large auditor goes into your code and reads it with a fine comb it's not a good idea to have blind trust in it. And Chinese author does mean CCP, assuming they live in China they are almost certainly able to be compromised and it is a bad decision to trust them with something as valuable as your whole code base.
- bioemerl 4y ago
  If you have evidence of foul play it's already far far too late to do anything. With authoritarian nations and their ability to control and steal your projects, you assume guilty until proven innocent. You should require there be a real audit before you trust gitea.
  - 5e92cb50239222b 4y ago
    Half of gitea's contributors are from Europe. Wait until you learn how much "Chinese" code is in the Linux kernel these days. This anti-Chinese hysteria is hilarious to watch from the sidelines, honestly. A few months ago there was a comment on HN by some American whose company was rewriting their frontend when they learned that antd (a React component toolkit) was developed by a Chinese company. https://github.com/ant-design/ant-design https://github.com/ant-design/ant-design

barnabee 4y ago

For info: there was some drama a while back [0], [1] and some (a lot?) of the community/devs went to https://forgejo.org/ https://forgejo.org/ Seemed to me like they had a point and it's worth considering following that project [2] instead. [0] https://gitea-open-letter.coding.social/ https://gitea-open-letter.coding.social/ [1] https://news.ycombinator.com/item?id=33372471 https://news.ycombinator.com/item?id=33372471 [2] https://codeberg.org/forgejo/forgejo https://codeberg.org/forgejo/forgejo

candiddevmike 4y ago
Will be interesting to compare the velocity between the two. Can a community fork keep pace and possibly even innovate more than the commercial upstream? There have been a few cases of open source collectives/coops that do what Gitea does but distribute the profits to contributors equally, wonder if any of those have reached sustainability.
gempir 4y ago
The issue is Forgejo doesn't really have the know-how or capabilities to drive this project forward. In the past months all they have done is rebrand Gitea and some minor fixes, but upstream (gitea) has added a huge number of features and merged tons of valuable pull requests. So are they just going to continuously merge upstream into their fork and do nothing besides that? The platform, Codeberg might be "well" funded but not to maintain another extra project and develop new features for it. I think the outrage was a little too big initially. It's a big task to create a git host that needs to compete with Github and the likes and I think it's fair that you want to make some money on the side with that. Compare these merged PRs: Forgejo https://codeberg.org/forgejo/forgejo/pulls?q=&type=all&sort=recentupdate&state=closed&labels=&milestone=0&assignee=0&poster=0 https://codeberg.org/forgejo/forgejo/pulls?q=&type=all&sort=... Gitea https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclosed+sort%3Aupdated-desc https://github.com/go-gitea/gitea/pulls?q=is%3Apr+is%3Aclose...
- tjoff 4y ago
  > I think the outrage was a little too big initially. It's a big task to create a git host that needs to compete with Github and the likes and I think it's fair that you want to make some money on the side with that. That seems completely irrelevant and orthogonal to the outrage though?

warent 4y ago

very excited about Actions. For several months I've been using a home server Gitea for a Unity project version control, because the project size is far too large for github/gitlab etc. So far everything about it has been excellent, and it's only getting better!

techknowlogick 4y ago
That's an awesome use-case! Are you using LFS in Gitea too with Unity? Are you working on anything publicly available? I'm looking for something new to play :) Disclaimer: I am a part of the Gitea TOC, and am employed to work on Gitea.

Kelamir 4y ago

As a novice at self-hosting, I previously attempted to use it, but got stuck as I didn't understand MySQL, and learning it just for Gitea was too much. However, I've had some progress with with another database recently, so I would like to give Gitea another try soon.

dual_dingo 4y ago
For small personal deployments, using SQLite as a database is usually sufficient. This means you don't need a fullblown SQL server, instead the whole database consists of a single file.
- geek_at 4y ago
  can confirm have about 20 repos and 1 org in my gitea and I never have problems with loading speeds

dave78 4y ago

What are the current thoughts on Gitea vs Forgejo? I'm thinking of migrating from a self-hosted Gitlab to one of them in the near future. The way Gitea was taken over leaves a bad taste in my mouth so I'm leaning towards Forgejo, but it's not really clear to me if that's the right choice.

CameronNemo 4y ago
I am personally not a fan of Forgejo relicensing (to AGPL). Makes the "soft fork" aspect so much harder, because anything contributed to Forgejo cannot be easily cherry picked onto Gitea.
jpace121 4y ago
Forgejo currently is only applying branding changes and currently plans on being a soft fork. I think it’s existence is a good thing for the ecosystem (if Gitea the Company did something wonky, there will be an organized group already doing releases ready to go), but I’m not sure there is a huge benefit in running it, at this juncture.
- dave78 4y ago
  The other discussion in this thread has convinced me that for now, the momentum seems to be with Gitea, so I'll probably lean towards that. I'm still disappointed in how the whole situation was handled, though, and it leaves me wondering what other changes will be around the corner.

justin_oaks 4y ago

I remember there being a big stink about Gitea, so much so that it was forked: https://news.ycombinator.com/item?id=34011581 https://news.ycombinator.com/item?id=34011581 I don't use Gitea, but if I were to start today would there be a proper reason to avoid Gitea?

Macha 4y ago
Gitea was taken from a community run project to an corporate owned one to allow for an open core future. Currently there's been no actions taken that negatively affect the open project, but the door is now open for a "This isn't working for our company, we're now going to SSPL" style move in the future.
- jolheiser 4y ago
  I am a community member of the Gitea TOC, and there will be no open core model. Gitea will remain fully open source with no tiers. The community TOC also has advantages in any such voting where something may negatively affect the OS project, although as you mentioned that hasn't happened yet, and I don't expect it will.
djha-skin 4y ago
https://news.ycombinator.com/item?id=35233168 https://news.ycombinator.com/item?id=35233168
jolheiser 4y ago
Currently the fork is simple rebranding with a few small changes here and there. Both of them will give you nearly the same experience, and they are a soft fork so all Gitea changes will be available. I'm biased as a community member of the Gitea TOC, so I'd of course recommend Gitea.

djha-skin 4y ago

I'm super excited Gitea is becoming better and better. Gotta be honest though; the really exciting feature I'm waiting for is ActivityPub[1] support. That will really make my single gitea instance much more interesting, when I can accept PRs from other instances and make them to theirs. A lot of comments about "Forgejo". In short: meh. Not a big deal[2]. I'll be sticking with Gitea. 1: https://github.com/go-gitea/gitea/issues/14186 https://github.com/go-gitea/gitea/issues/14186 2: https://news.ycombinator.com/item?id=35233168 https://news.ycombinator.com/item?id=35233168

lagniappe 4y ago
is it for-guh-joe or for-jeh-ho?
- jolheiser 4y ago
  I am not with the fork, but seeing as people ask this about us all the time I can relate. https://forgejo.org/static/forgejo.mp4 https://forgejo.org/static/forgejo.mp4
  - lagniappe 4y ago
    Is there ever internal discussion about the name?

sph 4y ago

Why is gitea, a self-hosted Github competitor, hosting its source on Github? Not a lot of dog-fooding going on over there.

jolheiser 4y ago
We are actively working on it, everything other than the main repo is on gitea.com and a lot of that is also being converted to dogfood actions. The main repo, however, has a lot of issues/prs/etc metadata and so migrating is a bit harder.
xx_ns 4y ago
They've been meaning to migrate for a while now, but have had various blockers. https://github.com/go-gitea/gitea/issues/1029 https://github.com/go-gitea/gitea/issues/1029

vorpalhex 4y ago

Ahhh this removes reverse proxy auth for the api! This is horrible! While reverse proxy auth should be disabled by default, this is critical. This breaking change makes gitea unsuitable for me going forward. Reverse proxy auth is perfectly secure when correctly setup and is sensible in many configurations.

joencott 4y ago
Not enough people are talking about this, as soon as the company took over they started to remove functionality. Shame on them.
- jolheiser 4y ago
  This was not a company decision, it was proposed by a non-company member and approved by two other non-company members (and one company member, but just pointing out context).
remram 4y ago
It seems it was only removed from the API. Are you really using it there? Can you say more about your use case?

legends2k 4y ago

Nice to see Blender team being thanked as major contributors for Gitea :)

techknowlogick 4y ago
The Blender Foundation has been wonderful! Among their many PRs to this release, one of the big ones was scoped labels.

frodowtf 4y ago

Wow. Great progress! Recently, I was wondering why gitea does not have a GitHub Actions alternative. What a timing. BTW, a colleague of mine told me that GitHub Actions wasn't supposed to be a CI/CD alternative at the time when it was released. I couldn't find any note on that online. Is it true?

Reitet00 4y ago
FWIW it's possible to use Woodpecker as an alternative to Actions. I guess Gitea Actions will be more tightly coupled with Gitea.
- techknowlogick 4y ago
  I was just telling someone else how great Woodpecker is. The protocol that Actions runners use to report logs/job statuses back to Gitea is an open protocol that maybe one day woodpecker could use it for enhanced integration with Gitea, so you could use woodpecker but have the experience be next to your code. Disclaimer: I am listed as a maintainer of Woodpecker. I am a also part of the Gitea TOC, and am employed to work on Gitea
thiht 4y ago
> GitHub Actions wasn't supposed to be a CI/CD alternative at the time when it was released Not sure what you mean by that, what was it supposed to be then?

Reitet00 4y ago

Wow, what a great changelog. I wish more software projects would take time to present their work to users like that.