GitHub Codespaces recently released multiple updates to improve visibility into monthly spend:
Organization administrators whose organization's codespace usage is paid for by the enterprise can now see month-to-date spending in their organization, even though their organization is not directly paying for this usage.
All organization administrators with access to billing reports can now see projected codespaces spend in the month. This calculation is an estimate based on the past seven days of codespace usage.
With these improvements, organization administrators can get a better sense of how large of a bill they can expect to pay at the end of the month, and remain aware of how much they are billing back to their enterprise.
Today's changelog introduces a new global page to find all of your projects!
🌐 Global Projects page
You will now find all of your relevant and commonly used projects in a single place at github.com/projects. This page is found from the global navigation menu under Projects and can be used to find projects you've recently viewed or created, regardless of the organization or where they live. No more searching across organizations and tabs for the project you are looking for!
✨ Bug fixes and improvements
Improved the table column ... menu and configuration options
Included Field sum configurations when copying a project or using a project template
Fixed a bug where uploaded files were not rendering in the project README or draft items
Fixed a bug where items could not be added to an empty roadmap view with a Group by field
Fixed a bug where invalid chart configurations prevented copying a project or using a project template
Fixed a bug where setting a project as a template gave an error message
See how to use GitHub for project planning with GitHub Issues, check out what's on the roadmap, and learn more in the docs.
Thismonth, wemadesomebig improvements to GitHub Copilot! Copilot Chat is now powered by GPT-4 and we updated the model used to detect off-topic chat queries. In VS Code, we are announcing the public beta of code referencing. We also introduced “agents” and the ability to generate commit messages with Copilot. In addition, we improved the context for explaining code and updated the Copilot menu UI. In JetBrains IDEs, we introduced partial acceptance of code suggestions.
Copilot Chat ispoweredbyGPT–4
WeupgradedtheCopilotChat experience, bringing more accurate and useful code suggestions with OpenAI‘s GPT–4model.
Off–topicmodelimprovementsforCopilotChat
As part of our safety features, we‘veimproved our off-topic model to detect chat queries which do not relate to programming. This should result in significantly fewerfilteredresponses.
Codereferencing in VS CodeisnowinPublicBeta
InAugust, we announced the Private Beta of code referencing in VS Code. This feature searches across billions of files on public GitHubrepositories for code that matches a Copilot suggestion. Sincethen, we’ve heard your feedback, and we’re shipping with a new and redesigned experience. One of the top points offeedback was that the original flow resulted in too many notifications. To fix this, if there’samatch, users will find its information displayed in the Copilot console log, including where the match occurred, any applicable licenses, and a deep link to learnmore. If you are interested in code references, you can refer to the window, otherwise, it won’t be in your way.
Thedeep link will now take you to a navigable page on GitHub.com to browse examples of the code match and their repository licenses, andsee how many repositories — including ones without licenses — that code appears in, as well as links to those repositories.
Wehaveintroduced a new capability called “agents” to enhance your interaction with Copilot Chat. Agents are like specialized experts who canassist you with specific tasks. You can mention them in the chat using the @ symbol. Currently, there are two agents available:
@workspace: This agent has knowledge about the code in your workspace and can help you navigate it by finding relevant files or classes. The @workspace agent uses a meta prompt to determine what information to collect from the workspace to help answer your question.
@vscode: This agent is knowledgeable about commands and features in the VS Code editor itself, and can assist you in using them.
Eachagentalsosupportsslashcommands. The slash commands you may have used before should now be used with an agent. For example, /explain is now @workspace /explain.
Improvedexplanationcontext in Copilot Chat in VS Code
You can ask Copilot Chat to explain a code selection in your active editor either through the @workspace /explain command or through the “Explain with Copilot” action in thecontext menu. Copilot Chat has now integrated implementations of referenced symbols, suchasfunctions and classes, which leads to explanations that are more precise and useful. This works best across files when you have an extensioncontributinglanguage services installed for one of the following languages: TypeScript/JavaScript, Python, Java, C#, C++, Go, or Ruby.
Commit message generation using CopilotinVS Code
Copilot can now generatecommit messages based on the pendingchanges using the new “sparkle” action in the Source Control inputbox.
UpdatedCopilotmenuinVS Code
OurCopilotmenuinVS Code is nowmorevisibleand aligned with our design for JetBrains IDEs. It is now easier to understand the current status of Copilot, access the various settings or documentation.
Thenewmenu is displayedwhenclickingontheCopilot icon in the lower rightcorner in the statusbar of VS Code.
JetBrainspartialacceptance for codesuggestions
TheCopilotextension for JetBrains IDEs has leveled up! You now havetheflexibility to incorporatecodesuggestions piece by piece, whether that’s word-by-word or line-by-line. Feel free to customize these shortcuts as you prefer. Happycoding!
Wewelcome your feedback on Copilot! Please join the discussionintheGitHubCommunity.
