SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

How to Auto-Select GitHub PAT by Repo Owner Using gh CLI and .gitconfig

0
·2 views

Developers managing multiple GitHub accounts over HTTPS often face authentication errors when Git defaults to the wrong Personal Access Token (PAT) for a given repository. A proposed solution embeds a custom credential helper directly into the .gitconfig file, eliminating the need for external scripts or manual account switching. The helper uses the repository owner extracted from the remote URL to run 'gh auth token --user OWNER', fetching the correct PAT automatically. Setting 'credential.useHttpPath = true' is essential so Git passes the full repository path to the helper, enabling owner extraction. An empty 'helper =' line before the custom helper ensures any pre-existing credential managers are reset, preventing conflicts on platforms like Git for Windows.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

EU Cyber Resilience Act reporting obligations become enforceable on September 11

The European Union's Cyber Resilience Act (CRA) begins enforcing its incident and vulnerability reporting requirements on September 11, 2025, ahead of the full compliance deadline of December 11, 2027. Manufacturers of 'products with digital elements' must now report actively exploited vulnerabilities within 24 hours, provide fuller notifications within 72 hours, and submit final reports within 14 days to a month. Non-compliance with reporting rules can result in fines of up to €15 million or 2.5% of global annual turnover. Pure browser-based SaaS products generally fall outside CRA scope and under NIS2 instead, but companies shipping installable components such as desktop apps, SDKs, browser extensions, or on-premise agents are likely covered. Security experts warn that many B2B SaaS firms may unknowingly fall within scope due to supplementary installable tools alongside their core web products.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer Shares Python Script to Quickly Audit Any New Server or Dev Machine

A developer named Arthur has published a beginner-friendly Python tutorial on DEV Community showing how to build a Developer Environment Checker tool. The script collects key system details — including OS type, CPU cores, RAM, disk usage, Python version, and local IP address — from a single run. It relies on standard Python modules such as platform, socket, shutil, and sys, along with the lightweight third-party package psutil. The tool is designed to save time when setting up or auditing a new server, VPS, or development environment by replacing multiple manual commands. Arthur presents the project as both a practical utility and a learning exercise covering concepts relevant to real-world server administration.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

OpenAI's Jalapeño chip outperforms NVIDIA on speed, throughput, and power efficiency

OpenAI has published benchmark results for Jalapeño, its first custom AI inference chip, showing it outperforms NVIDIA's GB200 and GB300 hardware across throughput, latency, and power efficiency simultaneously. Tested against the InferenceX public benchmark on three large open-weight models, Jalapeño delivered 1.5–1.9x more throughput per watt and 1.7–3.6x lower latency compared to leading NVIDIA hardware. The chip operates at or below 550W, roughly half the power draw of the GB300 at 1,400W. Designed in nine months, Jalapeño reflects OpenAI's broader strategy to co-design models, chips, and software together rather than rely on third-party GPU infrastructure. OpenAI plans to deploy the chip within its own infrastructure by end of 2025, with a second generation already in development.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Model Context Protocol goes stateless, unveils five-area roadmap for agentic AI

The Model Context Protocol (MCP) team published an updated roadmap this week, marking a significant architectural shift in its latest spec release dated July 28, 2026. The most notable change removes protocol-level sessions and the initialization handshake, making MCP servers stateless and sessionless by default, which enables straightforward horizontal scaling. The previous March roadmap's four goals — covering transport, agent communication, governance, and enterprise readiness — were fully delivered. The new roadmap outlines five priority areas with dedicated working groups: agentic messaging primitives, HTTP-native transport unification, agent identity and authentication, improved tool-response primitives with progressive discovery, and SDK developer experience. Notably, the agent identity workstream targets replacing API-key sharing between agents with standards-based approaches such as DPoP and Workload Identity Federation, with active participation in IETF OAuth and WIMSE bodies.

0 comments Read more at DEV Community