Finally reviewed LazyGit!
Amazing #dev & #devops tool for #git
https://jelloeater.me/review/lazygit/
検索
Is there anything more fun than sitting down for a couple of hours and fixing a complicated #git rebase?
We are looking to move to a new Git forge and need help with testing!
If you are a Fedora contributor, please consider helping with testing so we can take into account your feedback.
The testing instances we have are for GitLab and Forgejo.
➡️ https://fedoramagazine.org/inviting-testers-for-git-forge-usecases/
#Fedora #Git #OpenSource
返信元:
One step closer to having our #Jenkins be fully #Kubernetes at work. It's not like it was particularly difficult to set up, but more that there was enough bare metal resources allocated to the CI that it was a backlog item. Moving to k8s workers means those bare metal worker nodes can become k8s workers and be available for other workloads and devs can have more flexibility in directly defining their build environment requirements.
Deployed a #Rancher #k3s cluster with #Harvester, added a project/namespace for Jenkins, generated the kubeconfig with Rancher Manager, and then added it as a cloud provider in Jenkins. It was that easy. I made a basic pod template that runs a #Fedora image in the GUI, then created a Jenkinsfile in a #forgejo #git repo that did 6 parallel tasks. #Jenkins picked it up and it was fun to watch k8s pull the Fedora images and do it's thing from there.
Well, that's fun.
#Git
Today, I deployed #OpenGist, an open source project that's similar to #GitHub and with a UI similar to #Forgejo and #Gitea, and easily setup authentication through Forgejo. Very cool project!
https://github.com/thomiceli/opengist
#git #programming
I love that #Fedora #Linux is considering shifting to @[email protected]. As someone who has maintained Forgejo (and Gitea) for many years in a variety of environments, I am strongly in favor of this.
#forgejo #git #opensource
If you're wondering what #git forge to host your #opensource code project on, the right answer is probably going to be #forgejo. If the right answer was anything else, you probably wouldn't be wondering about it.
https://forgejo.org/
Don't want to host it yourself? Then #Codeberg is what you're looking for.
@[email protected] @[email protected]
PSA: Do not submit "omnibus" pull requests to #git repos, especially without talking to the maintainer first. Keeping PRs generally focused to one particular problem or feature makes things far more manageable for reviewing, testing, and reverting/bug-fixing later on. I would always much rather have 10 smaller PRs focused one specific thing each than one massive unsolicited one with a bunch of scope creep.
#opensource #programming
FYI, @[email protected] 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.
https://forgejo.org/2024-02-forking-forward/
#git #programming #gitops #opensource
Did you know that #git has a native GUI called gitk?
https://git-scm.com/docs/gitk/
投票
- Yes: 24票
- No: 22票
#AGPL は求められたときにソースコードを開示できればいいんだけど、いちいち開示するのは面倒だし、変更履歴も確認できた方がアドだから、 #Git リポジトリ ( #GitHub とは限らない) で公開するのが望ましいと感じている https://mattyaski.co/notes/9pkv7w9q6k
Better GitFlow or Why We No Longer Squash (all the) Commits.
#git #archive #information #startup
https://memorici.de/posts/better-gitflow/