Git and GitHub are key tools for sharing your work reproducibility and the greater good 🌱 However they are often seen as too 'hardcore' or developer-focussed to be used by researchers and data analysts. That's a misconception! Great vid to get started: https://www.youtube.com/watch?v=8Dd7KRpKeaE
GitNex 5.5.0 is now OUT with a new comment UI, the ability to update your profile avatar, the option to insert notes to issues/PRs/releases, and many other improvements.
We have also reached 400 stars on #codeberg. Thanks to all for supporting GitNex all the way.
With the upcoming 6.0.0 release, GitNex will have different version numbers, such as 6.0.0, 7.0.0, and so on.
I hope you enjoy the new release and find it even more productive.
basculement de #gitea vers #forgejo sous #docker, c’est assez simple. #synology
il suffit de changer dans votre docker-compose l’image de gitea pour forgejo.
After the #XZ attack, I have a suggestion for all #software forges (#Forgejo, #GitHub, #Gitea, #Sourceforge, etc.):
Have some way to visualize binary files better, including diffs to such files. Cuz now, we have basically nothing except byte counters.
Since they're binary files, it must be as generic as possible. But even some rendering or analysis is better than nothing.
The idea is to expose weird patterns in binary files that could be a sign of an attack.
As part of our extended roadmap to reduce technical debt and unify frontend technologies, many pull requests are being made to achieve this. We would like to celebrate the significant work done to remove a significant portion of jQuery in our codebase and the start of the switch to using Tailwind CSS. You'll start to see a significant amount of this work in the upcoming 1.22 release of Gitea.
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
Huh, apparently #Gitea switched to an open core model a while back, and the good people at CodeBerg e.V. made a fork called #Forgejo . Maybe I should switch?
Nice. #gitea did it; they're now makeing #giteaenterprise where they added already more features. And there's no doubt that they'll continue this path forward, putting more and more effort in the enterprise version and keeping the free version from getting these features via contributions since it would ruin their company.
And best thing is: they already are stealing code. They took stale PR's and put it into the Enterprise version. Thats just disgusting. And unlike gitlab, which EE is not only opensource (i.e. readable), they also have a lot of paid engineers to built their product, unlike gitea, where like 95% of work is done by volunteers, not only now but in the past included. It's espc disgusting for how cheap the features are, like an IP allowlist. Which gets even more sad when you think about what would happen if a volunteer would contribute similar features to the free version. Atleast we have not to guess as it is clearly stated in their contributors guidlines: they have added a clause once they became a company, that they can "politly refuse" any PR by simply not responding. That stinks for me after a tactic of keeping face while not allowing any code that would conflict with the enterprise version.
Migration from #gitea to #forgejo complete. Was a breeze using #nixos, really. Deployed forgejo to server, then stopped process, copied /var/lib/gitea to /var/lib/forgejo, fixed ownership and addressed a few small stateful data pitfalls: gitea database is named gitea.db, Forgejo is named forgejo.db so you need to move it. For repo origins using ssh, you'll need to update the origin to use ssh://forgejo@ instead of ssh://gitea@.
FYI, @forgejo is hard-forking from #Gitea, citing strong development community, commitment to FOSS, and growing feature-set beyond the Gitea base. They plan to keep the APIs compatible, but if you were on the fence about when to switch from Gitea to Forgejo, it's better to do that sooner than later.
Is it possible to fork a #GitHub repository on my own #Gitea server?
I want to be able to make PRs to it, but I'd prefer to do my actual development off of Github itself.
I guess my best option is mirroring, but I wouldn't know how to set up what's needed to get my mirror to be recognized as a fork of the original repo. @gitea#git
@kubikpixel cool tools, i will check them.
right now i use (work) tasks-plugin in #zimdesktopwiki and issues in #gitea.
private life is pen&paper in my calendar :)
How to file issues in Github from CLI
I know it is something I need to find in docs but probably I am dumb enough to not get it....