Cool. 20th anniversary of #git and #GitLab celebrated with an interview with Linus Torvalds: https://about.gitlab.com/blog/2025/04/07/celebrating-gits-20th-anniversary-with-creator-linus-torvalds/

Cool. 20th anniversary of #git and #GitLab celebrated with an interview with Linus Torvalds: https://about.gitlab.com/blog/2025/04/07/celebrating-gits-20th-anniversary-with-creator-linus-torvalds/
GitLab Duo with Amazon Q is here!
This integration of Amazon Q Developer with GitLab brings generative AI capabilities directly into GitLab, helping developers with feature development, code upgrades, reviews, and unit testing.
Learn more: https://bit.ly/4jql9Qb
OK everyone, I did it. I started a blog.
#heptapod 17.9.0 released, featuring #gitlab 17.9 and Mercurial 7.0 Changelog: https://foss.heptapod.net/heptapod/heptapod/-/blob/heptapod-17.9.0/HEPTAPOD_CHANGELOG.md Download instructions: https://heptapod.net/pages/get-heptapod.html#get-heptapod #git
Many universities and research institutes have their own #Gitlab or #Gitea instances, which is a good thing. But are there any plans for these instances to be federated ? It's a bit cumbersome to open a new account on a new instance every time I want to collaborate on a project. #openscience
Why does #gitlab make you authenticate. each. and. every. time?
So, you were wondering what to do with your life and stumbled upon GitLab's Encyclopedia Britannica of #OKRs
https://handbook.gitlab.com/handbook/marketing/developer-relations/developer-advocacy/social-media/ #GitLab #CorporateJargon #TimeTravel #LifeAdvice #HackerNews #ngated
@alexanderdyas That's true, but only for (more or less) 'advanced' users.
When you create an empty #GitHub or #GitLab repo, they literally tell you use 'git add .' in their 'Configure the Git repository' tutorial. There is no section how to setup a .gitignore file. Because .gitignore is very project/tech-stack specific.
Why is this even a problem, because the files stay in Git forever. Unless you invest a lot of time. And time = money.
The way Gitlab, Forgejo, Gitea etc. use the server-side SSH server to accept pushed data over SSH relies on a system user called git
having SSH access. (or forgejo
in their case).
Access is granted by the standard authorized_keys
inside ~/.ssh, which for forgejo means /var/lib/forgejo/.ssh/authorized_keys
. When a user adds an SSH key to their account, it's added to this authorized_keys file.
I really hate this, this means that any user of Forgejo is only inches away from having full shell access. The default shell of the forgejo
user is /bin/bash
, it exists inside of /etc/passwd
:
forgejo:x:122:130:Forgejo (Beyond coding. We forge.):/var/lib/forgejo:/bin/bash
I really really hate this. The only thing preventing random users of Forgejo having shell access is the default command of the SSH session as stipulated by the authorized_keys
entry, this is what it looks like:command="/usr/bin/forgejo --config=/etc/forgejo/app.ini serv key-1",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty,no-user-rc,restrict ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOgnZeNC4fMCXYuWxir7NlKts9Zj4sYZZJzzHh4IyTm2 Baa-New
forgejo
user. It will immediately disconnect you, and if you try submitting any specific command you'll receive Disallowed command
.control userpasswords2
and then explicitly disallow them RDP access. That RDP config is the only thing preventing them for remoting straight into your server. This si what it feels like, I can't help but wish SSH was entirely separate from everything else going on here.Can somebody explain why people create #spam #pullrequest|s? Who benefits from this? How does this scheme work?
For the offsite copy, we recommend using a remote service that is compatible with versioning tools such as Git, to ensure seamless integration with versioning tools. Once again, be aware of the risks associated with Microsoft GitHub's terms of service. Your institution may provide a #gitlab instance, also known as a gitlab forge, for storing your files. This option is highly recommended. Remember to download a copy of your files before leaving your institution for a new job.
10/11
*Decentralized source code hosting: we can do better.*
- #Github succeeded in providing us a space to swarm.
- #Gitlab #Forgejo and others gave us sovereignty back over our code hosting.
.
- @radicle now brings communication back between those independent hosts.
(Works like the #fediverse
.
This #git forge is a big step on the path to freeing uncensored project collaboration.
A much needed tool to bulletproof #foss
We have expanded our section on GitLab CI/CD pipelines with examples of
• GitLab Pages
• npm deployments with rsync
• building Docker containers
• multi-arch images with Buildah
• migrating GitHub Actions
https://www.python4data.science/en/latest/productive/git/advanced/gitlab/ci-cd/index.html
#GitLab #CICD #DevOps #DX