GitHub's AI Assistant Opened Devs to Code Theft
https://www.darkreading.com/application-security/github-ai-assistant-opened-devs-to-code-theft
#Infosec #Security #Cybersecurity #CeptBiro #GitHubs #AIAssistant #OpenedDevs #CodeTheft
GitHub's AI Assistant Opened Devs to Code Theft
https://www.darkreading.com/application-security/github-ai-assistant-opened-devs-to-code-theft
#Infosec #Security #Cybersecurity #CeptBiro #GitHubs #AIAssistant #OpenedDevs #CodeTheft
#Gitbutler now has it's own review system (compatible with GH PRs) from the creator of GH PRs.
https://blog.gitbutler.com/gitbutlers-new-patch-based-code-review/
So yet another external review system showing how broken #githubs PR system really is.
We now have #ReviewStack (does anyone actually use this), Graphite, and GitButler in the Github compatible alternate review system along with the client side systems (#jj, #ghstacks, #sapling, et al)
However I think GitButler totally misses the mark and continues the the sins of PRs into thinking that you need to groups PRs together into a logic unit.
Phabricator and Gerrit have both supported stacking diffs and the power of stacking was that a change could be related to a feature (i.e building up to implementing it) or just dependent on other features in the stack.
Forcing that a "branch" is has to be a single feature and your commits are reviewable but you still can't stack branches is STILL a hurdle to productivity which is the entire point.
Also no command line for gitbutler makes it my least favorite by far.
Anyone who actually bothers to click through and *read* that tech-bro dreck at "#TechCrunch" will see that "the snarky #GitHub comments" are not taking place on either the #Mastodon or #Bluesky #Githubs -- both of which I follow very closely and where this issue is completely absent
All the shouting is happening exclusively on the snarfed/bridgy-fed Github of the developer himself, where he's now busy closing comments on Issues as they've go off the rails and he can't keep up with everything that's being said
Here, for one: https://github.com/snarfed/bridgy-fed/issues/878
He's way in over his head, which can happen when you rush to code and publicize, without thinking through the real-world consequences for real people who are suddenly faced with your new Killer App(tm) coming into their lives
#prometheus #community just added all it's #helm releases to #githubs ghcr.io #oci #registry too.
See: https://github.com/orgs/prometheus-community/packages?repo_name=helm-charts
If you're interested in how to convert your #helm repo you can use:
https://gist.github.com/monotek/0cb1ac777a13ed3c38be450349c34839
helm #charts will be uploaded in the oci registry in chronological order (sorted by version).
Halloj! 😍💕
Denna veckan tittar vi på nya #Ubuntu, #Edge på #Linux och #Git. Vi diskuterar även #GitHubs kontroversiella nedstängning av #youtubedl och huruvida det finns andra alternativ. Detta, #foss, #opensource och mycket mer, häng med! 🚀