joe (@joe@jws.social)
I have been using GitHub (https://github.com/steinbring) for a long time, and I have been seeing a lot of people dunking on it lately (e.g., https://mitchellh.com/writing/ghostty-leaving-github) because of its many failings. I don't think that something like Codeberg (https://codeberg.org) or Bitbucket (https://bitbucket.org) is the answer because there is still a central point of failure and hosting bills to pay. I like the fact that things like ForgeFed (https://forgefed.org) and tangled (https://tangled.org) exist to at least federate comms.
I really don't know what the answer is.
#Github #ForgeFed #Tangled #Git #SourceControl
Show Original Post
dkz2r (@dkz2r@mastodon.social)
Are you commit messages all over the place? Do you dislike writing changelogs? Still deciding what semantic version your next release should be? Commitizen is a very handy tool that can assist and automate aspects of your release process.
https://commitizen-tools.github.io/commitizen/
- `cz commit`: add a new commit to your repo
- `cz bump`: intelligently increase your version number
- `cz changelog`: automatically generate a `changelog.md` file
#git #tools #code #trackcheck #RDM
— JH
Show Original Post
sanjay_ankur (@sanjay_ankur@fosstodon.org)
Hacked up a new script to update multiple #git repositories (or just the one) non-destructively. Doesn't handle all use cases, of course, but useful for a lot of general cases. It stashes any currently uncommitted work, and updates multiple branches---which can be specified as arguments.
https://github.com/sanjayankur31/100_dotfiles/blob/main/bin/git-update-repo.sh
#Linux #SoftwareDevelopment #Bash #ShellScript
Show Original Post
official_aptivi (@official_aptivi@mastodon.social)
GitHub is planning to be more transparent on service availability.
#GitHub #TechNews #TechUpdates #programming #Git
Show Original Post
2026 (@2026@officialaptivi.wordpress.com)
GitHub is planning to be more transparent on availability
Two unfortunate incidents that plagued GitHub happened in two different days during April, which caused instability in some areas of GitHub, including:
- April 23rd: GitHub had experienced problems related to merge queue operations for pull requests for affected projects, which caused squash-merged pull requests to produce incorrect merge commits when a merge group had more than one pull request. Because of this, subsequent merges have inadvertently reverted the pull requests’ changes.
- April 27th: GitHub had experienced problems related to search functions, including code search, as well as issues and pull requests searching, because of an incident that affected GitHub’s ElasticSearch subsystem. The cluster was overloaded, with the most possible chance being a botnet attack, which caused GitHub to be unable to perform searches.
According to the article that was published to the official GitHub blog, the team had to resolve a variety of bottlenecks by changing how systems work, such as:
- Authorization and authentication flows have been redone to reduce stress caused by database load.
- Webhooks have been moved to a different backend.
- User session cache has been redesigned.
Critical services have been dealt with by carefully analyzing different dependencies and risk levels, and started working on those improvements in order of risk. Those services like Git and GitHub Actions have been isolated to minimize the blast radius so that attacks will be less efficient. Also, cloud migrations have been initiated to make sure that high reliability and flexibility is achieved.
In order for the official GitHub status page to be more reliable and transparent, the team has also worked on updating the GitHub status page to include availability numbers and to include statuses that are either major or minor, so that users can have a more accurate representation of the service status. Also, GitHub is working on making sure that incidents can be more easily reported by users.
To learn more, visit the official GitHub blog article.
GitHub article GitHub status #Availability #git #github #news #Programming #Status #Tech #Technology #update
Show Original Post
thielen (@thielen@m.it.hs-worms.de)
@kaguya Naja, #git ist ja per se föderiert 🙂
Aber den Wunsch nach föderierten git-basierten Team-Collaboration-Plattforms (oder wie immer man die benennen möchte) habe ich schon öfter mal gelesen – z.B. auch bei OpenCode (Diskussion aus 2023/2024: https://discourse.opencode.de/t/mitwirkung-von-git-platform-federation/1984)
Dort wird auch auf Aktivitäten bei Forgejo hingewiesen:
https://codeberg.org/forgejo-contrib/federation
Und kleinere Dinge scheinen laut Roadmap schon via ActivityPub oder Erweiterungen davon föderierbar zu sein:
https://codeberg.org/forgejo-contrib/federation/src/branch/main/FederationRoadmap.md
#forgejo
Show Original Post
woosting (@woosting@mastodon.woosting.nl)
RE: https://mastodon.social/@itsfoss/116486598868528585
Nice! I often find myself making a workspace directory in my homedir for my #Git managed projects first thing after having installed #GNU/#Linux!
Show Original Post
mcepl (@mcepl@en.osm.town)
I don't care about excuses or otherwise, we shouldn’t use centralised code management on principle.
https://lucumr.pocoo.org/2026/4/28/before-github/
Thank you, @mitsuhiko
Show Original Post
habr (@habr@zhub.link)
История вайб‑кодера: «Я был скептиком, но до 4 утра спорил с GLM-5»
Привет! Я Женя, тимлид одной из команд Альфы. В статье расскажу, как наша команда скептиков вайб‑кодинга за две недели вывела в прод новый сервис и почему я переменил своё мнение. Про вайб‑кодинг слышал давно — соцсети заполнили ролики, где инфоцыгане наперебой рассказывали, как за пять минут сделать стартап с ИИ. Я понимал сложность энтерпрайз‑систем, где за каждым релизом стоят десятки согласований, техдокументация и ответственность за данные. Думал, что хайп будет недолгим.
https://habr.com/ru/companies/alfa/articles/1022948/
#вайбкодинг #glm5 #git #hr_tech #пилотирование_технологий #онбординг_разработчиков
Show Original Post
mrmasterkeyboard (@mrmasterkeyboard@mastodon.social)
Fun #Codeberg fact.
Add /!~codeberger~!/ to the end of any Codeberg URL and you will get their AI scraper garbage loop page!
#NoAI #FuckAI #AntiAI #Tech #Technology #Git #Forgejo
Show Original Post
kubikpixel (@kubikpixel@chaos.social)
GitHub is sinking
GitHub is racing towards the mythical zero nines of uptime. Users are starting to notice that GitHub is now a Microsoft product. Eww!
– by @db
🧑💻 https://dbushell.com/2026/04/29/github-is-sinking/
#github #microsoft #zeronine #dev #git
Show Original Post