Hey all, welcome to the latest Codespaces check-in! I’m currently baking away in sunny Scotland’s annual heatwave (they just keep getting hotter!) ☀️ but I’m still here to bring you the latest from the community and from the Codespaces team, so here we go~

From the Community 💬

• Huge thanks to @SoloLeveling7seven for returning to the community with an answer to their own issue on Codespaces getting stuck during setup. There were a lot of people facing similar problems so thanks for coming back to share the solution that worked for you! 🎉
• Thanks to @spenserblack for sharing your thoughts on @max-zinn’s question on Codespaces storage usage

Latest launches 🚀💥

Changes to Codespaces Access, Ownership, and Billing Settings

GitHub Codespaces is rolling out improved access controls for organizations 🎮. These changes will provide organizations additional control over which of their organization’s members or outside collaborators are allowed to use GitHub Codespaces on private and internal repositories. For more information on what this means for your organization check out the changelog post on the GitHub blog.

Maximum Codespaces per User Policy

Organization administrators can now specify the maximum number of organization-billed codespaces that any member of the organization, or collaborator, can create. For more information check out the changelog post.

That’s all of this time! Have any thoughts on anything announced above, or spotted anyone in the community you’d love to give massive kudos to? Shout it out in the comments below 📣. Until next time~