«Enviando parches via Email con Git»
https://andros.dev/blog/ce42d654/enviando-parches-via-email-con-git/
Cuando pensamos en trabajar con un amigo en un proyecto pequeño, instintivamente creamos un repositorio en GitHub o GitLab. Esta práctica, o reflejo, es relativamente moderna. Pero aunque parezca extraño, se puede colaborar/trabajar en proyectos sin usar hostings de Git. Aunque parezca impensable, antes no existían este tipo de servicios, y el software se desarrollaba con igual o más calidad.
#git
«Sending patches via email with Git»
https://en.andros.dev/blog/75beece9/sending-patches-via-email-with-git/
When thinking about working with a friend on a small project, we instinctively create a repository on GitHub or GitLab. This practice, or reflex, is relatively modern. But although it may seem strange, you can collaborate on projects without using Git hosting services. Though it may seem unthinkable, these services didn't exist before, and software was developed with equal or better quality.
#git
Git AI – công cụ CLI dùng AI tạo tin nhắn commit tự động. Phân tích thay đổi, sinh message ý nghĩa theo chuẩn Conventional Commit. Hỗ trợ đa nhà cung cấp (cả model cục bộ), chế độ tương tác để chỉnh sửa. Tiết kiệm thời gian “fix bug”, “update code”. #AI #Git #Tool #Lập_Trình #Công_Cụ #Developer
https://www.reddit.com/r/programming/comments/1qjtmgp/git_ai_an_ai_tool_that_generates_git_commit/
Git tip: Create a `.gitmessage` template file and set it with `git config commit.template ~/.gitmessage`. Consistent commit messages improve team communication and project history. #Git
Note to self: use `pre-commit autoupdate` to update pre-commit repositories to their latest versions.
#pre-commit #Git #SoftwareDevelopment
Head's up if:
1. You're using a package.json with a git+ssh:// package
2. You're using yarn 4
It'll break if you update to the latest git and try to do a yarn install. A "yarn set version berry" will fetch 4.12.1+ which will fix it.
#heptapod 18.7.1 released, bumping #gitlab to the regular patch/security version 18.7.2 Changelog: https://foss.heptapod.net/heptapod/heptapod/-/blob/heptapod-18.7.1/HEPTAPOD_CHANGELOG.md Download instructions: https://heptapod.net/pages/get-heptapod.html#get-heptapod #git #mercurial
#heptapod 18.6.2 released, bumping #gitlab to the regular patch/security version 18.6.4 Changelog: https://foss.heptapod.net/heptapod/heptapod/-/blob/heptapod-18.6.2/HEPTAPOD_CHANGELOG.md Download instructions: https://heptapod.net/pages/get-heptapod.html#get-heptapod #git #mercurial
Never thought I'd say this but #GitLab seems to be the better option for hosting a #Helm chart repository and a #Container registry than #GitHub... esp a private one. You could even do this from a single #Git repo (project) on GitLab, which also means you could even just create a single access token that is scoped to just this repo to have access to the hosted Helm charts and container images. Pretty nuts?
GitHub, otoh, I don't think you could even have a token that is as fine-grained scoped like this - to give access to a Helm chart (using the #OCI package registry route) or a container image means to give access to ALL of them belonging to the user/org. Am I wrong? Anyway, I wonder how does other options like #Forgejo compare to these two. Big W for GitLab though.
Mở source file cấu hình Vim dưới 30 dòng giúp viết commit message chuẩn: giới hạn 50 ký tự cho tiêu đề, xuống dòng trống, body tự xuống dòng ở 72 ký tự, kiểm tra chính tả. Dễ cài đặt, phù hợp ai dùng Git + Vim. Có thể tùy chỉnh theo Conventional Commits. #Git #Vim #OpenSource #CommitMessage #LậpTrình #CôngCụ #DevTool
heise+ | Textprojekte gemeinsam stemmen mit Git: So gehten Dokumentationen und mehr
Wenn mehrere Personen isoliert an umfangreichen Texten arbeiten, führen Versionskonflikte und verlorene Änderungen schnell zu Problemen. So hilft Ihnen Git.
#Git #IT #macOS #Mobiles #Software #Versionskontrolle #news
Today when fetching my torvalds/linux.git remote from git.kernel.org it felt strange... it received 2918038 objects (781.11 MiB) for 24d479d26b25b..a66191c590b3b by following #diff stats:
70 files changed, 658 insertions(+), 281 deletions(-)
My gut feeling is that that's not a "normal size" for this diff stat... Am I the only one experiencing this? Is this actually expected behavior, or am I just being overly suspicious? Any idea, anybody? Especially @monsieuricon or @gregkh?