Forgejo v1.21 is available and comes with significant improvements to Forgejo Actions and the Forgejo runner. It also brings better user blocking, many documentation improvements, a shortcut button to open new PRs, mail notifications when new users are created and more.
Never heard of this one before, looks like a really neat project!
It’s a fork of gittea aiming to accelerate federation support.
I’m running it in my homelab for projects I do not (yet) push anywhere public, and projects containing private items such as ssh keys. It is snappy and has a ton of features. I can imagine when the federation support works, one can set up their own git forge and contribute more easily to other forges no matter what software they run.
And, to be honest, that is already how git works if you use the email workflow. Here we just get a web based flow with federated issues and pull requests. But if email is enough for you, you can have a full federation with email and git.
New Lemmy Post: Forgejo v1.21 is available (https://lemmy.world/post/8799740)
Tagging: #SelfHosted(Replying in the OP of this thread (NOT THIS BOT!) will appear as a comment in the lemmy discussion.)
I am a FOSS bot. Check my README: https://github.com/db0/lemmy-tagginator/blob/main/README.md
I’m curious, why is this bot currently being downvoted for almost every comment it makes?
I don’t know about other people, but I find these comments noisy. I’d rather just see replies to the post from actual people.
Please, just block the bot and you won’t see it again. If there was a way to make the replies from the bot not appear on lemmy, I would add it, but it’s not possible.
Hey no problem :) I totally understand and read through the linked README. FWIW I find the fact that Lemmy is in Rust, pretty… tricky. Getting Lemmy to run on my OpenBSD server started with a couple of crazy segfaults!
yeah I guess maybe the formatting and the verbosity seems a bit annoying? Wonder what the alternatives solution could be to better engage people from mastodon, which is what this bot is trying to address.
edit: just to be clear, I’m not affiliated with the bot or its creator. This is just my observation from multiple posts I see this bot comments on.
I wonder if perhaps wrapping the majority of the text in a spoiler would work. Though I don’t know if that translates over to Mastodon (if not, it might look a bit funky on that side).
Unfotunately mastodon doesn’t support markdown, and even trying to do hyperlinks is an exercise in frustration. The integration between lemmy and mastodon sucks atm. It’s part of why the bot exists.
Ah I see, that’s unfortunate then. For what its worth, I still think the bot is a great idea for discoverability and bridging the two services together! I hadn’t seen it before since I usually have bot users muted and happened to see this comment chain while logged out.
I’ve given it a follow from my Mastodon account since I do tend to miss quite a few cool Lemmy posts it seems, and I think it’ll help me find some communities in general that I’ll want to subscribe to from over here.
I just really hope they get Slack and JIRA support.
Slack yes.
Jira requires atlassian to enhance their product in a fashion other than contract terms and pricing. Since most of their clue left - see “dead Sea effect” - and the remainders are seemingly coping with maintenance and some bug-fix, I just don’t see that happening. And I’m okay with letting a bloated java web site just … die.
wait Jira is a Java website?
That explains so much…
On that note: Why is it every single time a piece of Software I find runs or feels like absolute Garbage it turns out it was written in Java? (Ok all things being fair occasionally the ancient PHP App is in the mix as well but it’s 95% Java Apps being shit)
There is support for Slack via repository webhooks.
Eh, it’s not the same as the built in links with JIRA or GitLab. Also JIRA won’t link to it either. Hopefully one day it’ll get proper support.
I am yet to see the point of this. Does this offer anything that gitea doesn’t?
Is a soft fork, its purpose is to specifically stay in step with the upstream and working on new features the upstream isn’t ready/doesn’t want. As far as I know, they’re the devs working on federation between selfhosted/any other instances.
You can find the answer to that question in the linked release notes. (What is unique to Forgejo)
Do the actions still look like Ansible?
Then no.