GitHub

GitHub Universe is typing... Cooking up something fun for you to build ⌨️ Make sure you grab your in-person pass ⬇️ https://lnkd.in/eqcvEftd

Ever been to a hackathon? Follow participants throughout their day, from badge to the final demo. What you can learn from attending a hackathon ⬇️ https://lnkd.in/e3PGw9ZM

GitHub just released external custom properties and Port is proud to be the first partner integration. What are external custom properties? GitHub repos already support custom properties. These are fields like owner or service tier that you can filter on and use to target rulesets. External custom properties are the same fields, but now owned by an outside system. An integration like Port writes them through an API, they're read-only in GitHub, and they sit under that integration's own prefix (like port.criticality). Why does it matter? Most orgs already know which team owns a service, how critical it is, and whether it's in compliance scope. But that context often lives somewhere else, not in GitHub where the work on the repo happens. Copying it over by hand or with scripts may work in the short term but doesn't last. With this new integration, the context on every repo updates whenever it changes in Port, and because it's read-only in GitHub, the two never disagree. What can you do with it? You can filter your repos to see everything a team owns or every tier-1 service, and apply rulesets by property, so a rule for production services covers a repo the moment it's marked production in Port. Most importantly, this change helps agents know more when they start their work. An agent opening a change in payments-api can see that it's a tier-1 service owned by team-payments and in SOC 2 scope without a separate connection to your catalog, so it brings in the right reviewers and expects the right checks from the start. You can read more about this in 2 places: GitHub's Changelog: https://lnkd.in/dfDHMsuA Our blog: https://lnkd.in/ecmJ5iVr

#GitHubUniverse is just around the corner. 👀 What will you be adding to your agenda? From verifying AI-written code to securing npm dependencies, here are the sessions to keep in mind at this year's event. ⬇️ https://lnkd.in/eDcyrEKs

As software creation speeds up, secret protection needs to scale with it. GitHub’s new context-aware classifier evaluates candidate secrets in under 2 milliseconds and could more than double the number of secrets we can prevent before they enter repository history. Here's how secret protection can keep pace as developers and agents move faster. https://lnkd.in/eAz73thz

We're excited that our partner and customer GitHub will be joining our upcoming October Community session. Rohan Parakh, Staff Product Manager at GitHub, and Revital Ben Ami from our Product Solutions team will show what our two teams built together. They'll show you how the context you already manage in Port, like service tier, ownership, compliance status, business criticality, and agent-readiness, now shows up right on your GitHub repos. That way, your agents get more important context before they start working. We'll also cover what else shipped recently, what's next, and of course, answer your burning questions. Aaand we'll share one more thing. Here's a hint: 🕹️ Join Rohan and Revital on Thursday, October 22 at 12pm ET / 6pm CEST Grab your spot here: https://lnkd.in/ebiWKkvy

What happens when low-quality contributions become one of the biggest pain points for open source maintainers? Camilla Moraes from GitHub’s Tiny Wins team joins the latest GitHub Podcast to talk about tackling the AI slop problem, listening to maintainers, and deciding what to fix next. Watch the full GitHub Podcast on YouTube, listen to it wherever you find your podcasts, or find it at gh.io/podcast

⚡️ Anthropic's Claude Haiku 5.5 is now generally available in GitHub Copilot. ➡️ It's a lightweight model designed for fast, high-volume work like subagents, quick edits, and terminal tasks. ➡️ Our early testing showed that it matched Claude Sonnet 5 on many coding tasks while using significantly fewer tokens and steps. Try it out in the GitHub Copilot app, CLI, or Visual Studio Code. https://lnkd.in/e3WrxXuX

Local sandboxing for GitHub Copilot is now generally available 🙌 This allows Copilot to run commands in an isolated environment with controlled access to files, networks, system capabilities, and credentials so you have more granular control. It also gives enterprise teams a way to centrally manage policies. Try it out in GitHub Copilot CLI, GitHub Copilot app or Visual Studio Code. https://lnkd.in/eW_wEdxM