Google AI Studio Adds Import from GitHub to Build a Deployable App

Benchmark-backed Ollama has amassed 176,000 stars, and nearly 17,000 forks on Github by helping developers easily run AI on their PCs.

The post GitHub Reports 6 Service Incidents in June 2026, Details Mitigations appeared on BitcoinEthereumNews.com. Darius Baruo Jul 08, 2026 20:23 GitHub faced six incidents in June 2026, impacting Copilot, API, and more, as AI-driven workloads strain infrastructure. GitHub revealed in its June 2026 availability report that the platform experienced six significant service incidents last month, impacting core features like Copilot, API services, and repository operations. The report outlines both causes and corrective actions as the company grapples with increasing infrastructure demands driven by AI workloads. The most critical disruptions included a June 4 failure affecting 81.6% of Copilot code review requests and a June 8 outage that caused 17% of unauthenticated user requests to fail. GitHub attributed the former to an unvetted dependency update and the latter to a spike in abusive automated traffic targeting specific endpoints. Other incidents spanned authenticat

GitHub continues to be a scintillating target for attackers because it sits in the middle of the software supply chain and gives threat actors three things they crave: source code, secrets, and automated pipelines to run amok in. Datadog Security Research has been tracking what it calls a “sustained pattern” of GitHub API abuse over the past several months that seeks to map organizations and their members. While individually these requests are “unremarkable,” they become dangerous when they move across environments for weeks at a time, and, worse, progress to full-out cloning. The biggest challenge is that they blend into normal API usage patterns. GitHub has been a goldmine for criminals looking to breach organizations because many development lifecycles are insecure, said David Shipley of Beauceron Security. Typically, threat actors are after API keys and cloud secrets. “Now with everyone being pushed to do more, faster, with AI agents coding, the treasure trove of secrets is likely

Google AI Studio is rolling out Import from GitHub in Build mode. It transforms an existing repo into a runtime-compatible format. You can then iterate on it, deploy it, and more. Here is what changes for developers. The post Google AI Studio Adds ‘Import from GitHub’ to Build Mode, Turning an Existing Repo Into an Editable, Deployable App appeared first on MarkTechPost.

A prompt injection attack can trick GitHub’s preview Agentic Workflows into retrieving content from private repositories and publishing it publicly, exposing a broader risk as enterprises deploy AI agents with privileged access to software development environments, according to new research from Noma Security. The AI security company detailed the attack, dubbed GitLost, in a blog post, saying an unauthenticated attacker could exploit GitHub’s preview Agentic Workflows by submitting a crafted GitHub issue to a public repository. If the AI agent has read access to private repositories within the same organization, it can retrieve sensitive information and publish it in a public comment, the company said. GitHub Agentic Workflows combine GitHub Actions with AI models such as Claude or GitHub Copilot, allowing developers to define workflows in Markdown. At the same time, AI agents read issues, invoke tools, and perform tasks on their behalf. “What will happen when the GitHub agent reads so

The post Q1 2026 Data Shows Open Source Collaboration Hits New Highs appeared on BitcoinEthereumNews.com. Timothy Morano Jul 07, 2026 16:55 GitHub’s Q1 2026 Innovation Graph reveals 16% growth in cross-border developer collaboration, the fastest pace since Q2 2020. GitHub’s Innovation Graph for Q1 2026 confirms a surge in global open-source collaboration, with cross-border developer activity growing 16% quarter-over-quarter. This marks the second-highest growth rate since tracking began in 2020, trailing only the 21% spike seen in Q2 2020 during the initial pandemic-driven tech boom. The ‘economy collaborators’ metric, which tracks the total volume of git pushes and pull requests between developers across different economies, highlighted this acceleration. The data suggests that open-source software development is continuing to break down borders, with a sharp rise in international contributions. Key Highlights by Economy While the growth is global, regional trends st

Microsoft has fitted the June 2026 update to Visual Studio IDE with a GitHub Copilot usage window that gives a clearer view of where a user stands against the GitHub’s new usage-based model. The update also adds trust validation for Model Context Protocol (MCP) servers. GitHub Copilot usage now is calculated based on token consumption rather than by request, as part of GitHub’s new usage-based billing model, Microsoft said on June 30. The refreshed usage window in Visual Studio gives a clearer view of the stance against that model, with real-time updates as the developer works. This can be opened by selecting Copilot Usage from the Copilot badge menu. GitHub Copilot switched to usage-based billing on June 1. Also with the June update, Visual Studio now validates MCP server trust in two places during startup. Before the MCP server process starts, the current configuration is compared against a previously trusted baseline. After it starts, the fingerprint of its tools, prompts, resourc

Stung by a surge in cyberattacks that have run amok in developer environments, GitHub has strengthened the security of actions/checkout to block ‘pwn request’ attacks that exploit insecure use of the pull_request_target workflow trigger to run an attacker’s code with the workflow’s full privileges. Announced on June 18, actions/checkout v7 now automatically blocks and fails workflows when used inside pull_request_target or workflow_run events when attempting to fetch unreviewed fork pull request code. From now on, the only away around these checks will be for developers to implement an opt out by adding an explicit allow-unsafe-pr-checkout to actions/checkout, GitHub said in its V7 changelog. The change signals the beginning of a new ‘secure by default’ era in which security will be defined by the GitHub system rather than being left to discretion of developers. As part of that effort, on July 16, the new defaults will be backported to all supported major versions. “Workflows pinned to