GitHub Copilot Usage Metrics Now Available at Repository Level

·1 views

GitHub made repository-level Copilot usage metrics generally available on July 17, 2026, allowing organizations to track AI assistant usage broken down by individual repositories. While this granularity improves resource allocation visibility, exporting every combination of repository, team, model, editor, and date can generate high-cardinality telemetry that strains monitoring systems. Engineers are advised to establish a field budget, bounding dimensions like model and editor to documented enums while aggregating or pseudonymizing user-level data. A recommended pipeline flows from the GitHub usage API through a bounded collector into a normalized warehouse table before reaching dashboards. Best practices also include backfilling data one day at a time using an idempotency key and testing edge cases such as renamed repositories, deleted repositories, and API timeouts.

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)

Why React apps need separate libraries for server state and client state

React and React Native apps manage two fundamentally different types of state: server state, which is a temporary local copy of remotely owned data, and client state, which the app owns entirely. Server state requires built-in caching, deduplication, background refetching, retry logic, and garbage collection, while client state simply needs to be held, kept reactive, and occasionally persisted. Using a single general-purpose store with hand-rolled cache logic works on small apps but becomes increasingly difficult to maintain as an application scales. Two recommended pairings handle this split well: Redux Toolkit with RTK Query, or Zustand paired with TanStack Query, both of which give each state type its own dedicated tooling. Treating the two as interchangeable and forcing them through one solution means manually rebuilding features that purpose-built libraries already provide out of the box.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Perl v5.44 Maintenance Release Arrives; April Task Force Targets CPAN Security

Perl v5.44 was released on 15 July as a maintenance update, marking a closely watched milestone for the Perl community. Alongside the release, a project called Parallel Perl (pperl) has gained attention as a next-generation Perl 5 runtime built in Rust, featuring JIT compilation and auto-parallelization. Salve J. Nilsen announced the formation of the April Task Force, aimed at strengthening the CPANSec CNA function and improving the security posture of CPAN and Perl. The task force is also preparing the community for potential risks posed by security analysis-capable large language models. The week's newsletter additionally highlights several community contributions, including tutorials on DBIx::Class, Flatpak containerization for Perl scripts, and SOLID design principles in Perl.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Native CSS Features Now Cover Most Reasons Developers Adopted Tailwind

Modern vanilla CSS has gained native support for features like nesting, the :has() parent selector, and @layer cascade control, reducing the need for utility frameworks like Tailwind. By end of 2024, CSS nesting was supported across all major browsers, while :has() reached roughly 94–98% cross-browser availability. A July 2026 developer forum post demonstrated that an entire Tailwind dashboard could be rebuilt in plain CSS, and a March 2026 benchmark found vanilla CSS still outperforms Tailwind v4 in build speed simply because it requires no compilation step. Bundle size comparisons also favor plain CSS, with one landing page test showing Tailwind's output was 75% heavier. The article argues that while Tailwind remains a valid choice for large teams with established workflows, solo developers and small projects may no longer need the added toolchain.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Nigerian Developer Reflects on Rejections, Losses, and Resilience in 2025

A Nigeria-based developer recounts a difficult stretch in 2025 marked by a contract cancelled over his choice of operating system and a rejection from a funded residency program in Helsinki. He also missed out on a Community Program Manager role at DEV after MLH's acquisition, with hiring infrastructure in Nigeria cited as the barrier. Despite repeated setbacks, he continued competing in DEV Challenges, winning at least one and drawing lessons from his losses. An article he wrote from Port Harcourt was featured in a curated AI newsletter tied to the AI Engineer World's Fair conference in San Francisco. He credits the DEV.to community with providing quiet support through consistent engagement rather than direct conversation.

0 comments Read more at DEV Community