clion_feed (@clion_feed@techhub.social)
CLion 2026.1 Is Here
#Clang #CLion #News #Releases #Acp #Bazel #Cmake #Dap #Git #Unittesting
https://blog.jetbrains.com/clion/2026/03/2026-1-release/
Show Original Post
foto_wawa_arthur (@foto_wawa_arthur@mastodon.social)
@comics #security #git #development
Show Original Post
heisec (@heisec@social.heise.de)
Sicherheitsupdates GitLab: Angreifer können E-Mail-Adressen hinterlegen
Die Entwicklungsumgebung GitLab ist über mehrere Sicherheitslücken angreifbar. Admins sollten ihre Installationen auf den aktuellen Stand bringen.
#Git #IT #Patchday #Security #Sicherheitslücken #Updates #news
Show Original Post
habr (@habr@zhub.link)
Предсказываю неочевидные факты о вас и вашем отделе по коммитам
Статья о том, какие неочевидные вещи можно узнать о вас из логов гита. Методы ниже не бьют на 100%, но «щито поделать, десу».
https://habr.com/ru/articles/1012546/
#git #визуализация_данных #управление_командой #статистика #аналитика #метрики #менеджмент #разработка
Show Original Post
heptapod (@heptapod@fosstodon.org)
#heptapod 18.8.3 released, bumping #gitlab to the regular patch/security version 18.8.7 Changelog: https://foss.heptapod.net/heptapod/heptapod/-/blob/heptapod-18.8.3/HEPTAPOD_CHANGELOG.md Download instructions: https://heptapod.net/pages/get-heptapod.html#get-heptapod #git #mercurial
Show Original Post
smartgit (@smartgit@techhub.social)
Stop googling "how to undo git commit" for the 100th time! 🤡
Level up your Git game with interactive quizzes and practical how-to guides at https://git-skills.dev 🚀
Whether you're a Git newbie or a rebase wizard, we got your back ✨
#git #SmartGit #GitQuiz #coding #devlife
Show Original Post
Doctor0710 (@Doctor0710@mas.to)
RE: https://mas.to/@Doctor0710/116103181360176542
Almost a month after I decided to just delete my Github alltogether, especially after the news about their AI training policy and it being opt-out instead of opt-in. Still very much pleased with #Forgejo
Show Original Post
sayzard (@sayzard@mastodon.sayzard.org)
Jacob (@fat)
기계용 Git 제공 서비스인 Code.Storage를 소개한다. 분당 1만5천 개 이상 레포지토리가 생성되는 등 대규모 개발자/AI 자동화 워크로드를 겨냥한 새로운 도구로 보인다.
https://x.com/fat/status/2036846209265262729
#codestorage #git #developerplatform #automation
Show Original Post
ngate (@ngate@mastodon.social)
🤔 Ah yes, let's rebuild #Git in #Zig because clearly the root of all #AI inefficiencies is verbose command output. 🛠️ Fielding's breakthrough: machines don't appreciate tissue paper. 🚀🌟
https://justfielding.com/blog/nit-replacing-git-with-zig #Efficiency #Breakthrough #CommandOutput #HackerNews #ngated
Show Original Post
h4ckernews (@h4ckernews@mastodon.social)
Nit – I rebuilt Git in Zig to save AI agents 71% on tokens
https://justfielding.com/blog/nit-replacing-git-with-zig
#HackerNews #Nit #Zig #Git #AI #Savings #Tokens
Show Original Post
t (@t@toot.berlin)
Sagt hier gerade der Codegaragenvermieter: Ich borg mir mal standardmässig deine Autos, um meine Fahrkünste zu verbessern ausser du verbietest es mir explizit?
Irgendwie haben sie vergessen zu erwähnen was sie mir dafür bezahlen.
Show Original Post
ajn142 (@ajn142@infosec.exchange)
Hey #devops #git peeps, mind if I pick your brains for a bit?
I maintain a couple of internal GitHub repos at $Employer for various windows app install scripts (PowerShell), that are used to deploy our EDR, DLP, and other such tools. These all grew out of a script template (or if I’m feeling fancy, framework) that was meant to abstract away some differences in behavior between a couple legacy MDM platforms and our planned future platform.
Changes to these scripts fall into three gross categories:
- Bumps of the app version, generally without any other changes.
- Changes to the template logic.
- Changes to the app-specific logic.
I’m gonna skip version changes, because they’re essentially a subclass of app-specific logic.
My workflow in developing the template generally goes something like this:
- Work on an app-specific logic change.
- Determine this is actually something more broadly usable than just that one app, and move the change out of the app-specific logic and into the template logic.
- Increment the template version in the front-matter of the app-specific script.
- Diff the app-specific script against the template, and merge in the changes in the template logic, ignoring the app specific logic (actual logic in the app script, placeholder in the template)
- Diff the updated template script against each of the other app-specific scripts, and merge in the template logic, ignoring the app-specific logic (placeholder logic in the template, actual logic in the app script).
What I’m interested in is automating step 5, so that on push of an updated template version, all my scripts update too. Automating step 4, so that on push of an app-specific script containing updated template logic, the template repo gets updated would be pretty cool too.
What I don’t understand is how I could programmatically merge in only the desired changes (template logic) , and not undesirable ones (app-specific logic)?
Show Original Post