kkarhan (@kkarhan@infosec.space)
@green no, because #git as #VersionControl demands that...
Show Original Post
orhun (@orhun@fosstodon.org)
Damn... I needed this for so many years 🥹
⚡️ **git-interactive-rebase-tool** — A full-featured sequence editor for Git rebases
💯 Reorder commits, squash/fixup visually, inspect diffs & edit actions.
🦀 Written in Rust & runs in the terminal!
⭐ GitHub: https://github.com/MitMaro/git-interactive-rebase-tool
#rustlang #git #tui #terminal #devtools #versioncontrol #opensource
Show Original Post
musicmatze (@musicmatze@social.linux.pizza)
I feel like a lot of developers fear merge conflicts and complexity of "rebase".
That's why projects employ the rebase-merge or rebase+squash-merge workflow.
First of all: That's a unfounded fear.
Second of all: How can you expect your users to trust you w.r.t. professionalism in writing source, when you do not even show them (or have) your professionalism when using the basic tools _for_ writing source code.
Like... everyone is ranting about "AI" producing sub-par code, but then commit histories look like shit all the time with people doing "format fixed", "fixes", "more stuff" commits.
... or, in other words: LEARN TO USE THE TOOL YOU FKNAAAARGGHH MORONS!
---
Despairingly presented by someone who just tried to find out why a certain function was implemented in a certain way...
#git #github #software #sourcecode #opensource #development
Show Original Post
dvalin99 (@dvalin99@mastodon.uno)
Il cassetto segreto di GIT: Stash 📥
Lo Stash è il salvavita di #git che ti permette di "congelare" il tuo codice attuale e saltare da un task all'altro in totale libertà. È come un cassetto magico: metti dentro, chiudi, risolvi il bug urgente e poi riprendi esattamente da dove avevi lasciato 
Link 👇
https://peertube.uno/w/c7G2UwMrt2BEFSiyt6iTDu
#opensource #peertube #UnoOpen
Show Original Post
tomminieminen (@tomminieminen@mastodontti.fi)
Työttömäksi ilmoittauduttu ja #KDE:n kotoistusrepolle saatu tehdyksi merge- ja scatter-toimenpiteet. Jälkimmäinen oli viivästynyt, koska #KDETechBase'ssä ollut ohje oli auttamatta vanhentunut eikä omatoimisesti päivittämänikään enää toiminut sen jälkeen, kun projektissa siirrettiin .pot-mallipohjatiedostot #Subversion'ista #Git'iin. #miehenelämää #kotoistaminen #L10N
Show Original Post
devdigest (@devdigest@mastodon.social)
⚡️ Fixing High CPU Burn on GitHub Actions Runners
🏷️ #devdigest #dotnet #net #git #github
https://devdigest.today/goto/5236
Show Original Post
escolalinux (@escolalinux@mastodon.social)
🔍 Desmistificando o Debate Git vs. GitHub: Entendendo as Principais Diferenças 🖥️🔗
Git e GitHub são frequentemente confundidos, mas possuem funções distintas no mundo do desenvolvimento. Descubra as diferenças essenciais entre eles e como cada um pode beneficiar seus projetos!
👉 Saiba mais no blog: https://nova.escolalinux.com.br/blog/desmistificando-o-debate-git-vs-github-entendendo-as-principais-diferenas?utm_source=dlvr.it&utm_medium=mastodon
#Git #GitHub #Desenvolvimento #Tecnologia #CódigoAberto
Show Original Post
devdigest (@devdigest@mastodon.social)
⚡️ Git Integration Still Feels a Decade Away
🏷️ #devdigest #dotnet #net #microsoft #ide #visualstudio #git
https://devdigest.today/goto/5235
Show Original Post
devto_vn_bot (@devto_vn_bot@mastodon.maobui.com)
Trước Git, chia sẻ mã nguồn qua USB/email: khi đồng nghiệp sửa lỗi A lại sinh lỗi B, không rõ nguyên nhân hay phiên bản nào mới. Git ra đời giải quyết bằng cách:
- Theo dõi mọi thay đổi & tác giả
- Loại bỏ "final_final" phiên bản
- Lưu trữ lịch sử chỉnh sửa
Vấn đề chia sẻ mã còn tồn tại → GitHub xuất hiện với máy chủ trung tâm giúp đồng bộ hóa mã giữa các lập trình viên. #Git #VersionControl #GitHub #QuảnLýPhiênBản #LậpTrình
https://dev.to/satyasootar/version-control-for-beginners-the-p
Show Original Post
kkarhan (@kkarhan@infosec.space)
@philpem Maybe this is something to point the #git maintainers towards as an issue?
Tho this may be an architectural limitation or decided-upon explicit goal:
As with most other distributed version control systems, and unlike most client–server systems, Git maintains a local copy of the entire repository, also known as the "repo", with history and version-tracking abilities, independent of network access or a central server.
So I'm not shure if "clone only history between commit A / branch A and commit B / Branch B" is even possible, cuz whilst git does support parallell, distributed and non-linear workflows, it's having a central, linear branch-based versioning and may just be unable to facilitate that without having the previous history on hand.
- If #Subversion can do that, then expect it to be explicitly unsupported in
git, because @torvalds basically spec'dgitwith the words 'if in doubt, do the opposite of Subversion'…
Show Original Post
kkarhan (@kkarhan@infosec.space)
@philpem the good part about the #kernel #git is that they do proper branching by version numbers, so you can directly jump to a version without having to download a tarball again.
- More projects should do it that way!
I only use #tarballs for #OS1337 out of convenience and to make it easier to reproduce. Plus not every build system / target machine is allowed to have network access so importing fewer files is easier...
- cloning said git takes ages and a ton of storage!
Show Original Post
devto_vn_bot (@devto_vn_bot@mastodon.maobui.com)
Git worktree cho phép làm việc đồng thời trên nhiều nhánh trong cùng dự án AI, giảm việc chuyển đổi ngữ cảnh khi chạy training, tiền xử lý dữ liệu hay sửa lỗi. Tuy nhiên cú pháp phức tạp nên tôi tạo công cụ **gwt** giúp quản lý worktree nhanh hơn: liệt kê, tạo, chuyển, xóa nhánh chỉ bằng lệnh ngắn gọn và hỗ trợ autocomplete. #git #worktree #AI #devtools #programming #côngcụ #pháttriển #lậptrình
https://dev.to/konstantin/handling-multiple-branches-in-ai-projects-with-git-worktree-40pn
Show Original Post