Github blog/2020-05-06-…

Translation: Liu Xiaoxi

GitHub is known to host thousands of software communities, from open source projects to enterprises, from small teams to large organizations. This year’s Satellite was all about providing tools for the community and solving problems that are important to developers.

Earlier this year, we made GitHub free for teams to make sure cost wasn’t a barrier to teamwork on GitHub. We are expanding GitHub sponsors to more than 30 countries to help developers make a living from open source. We launched the GitHub mobile app, which has helped hundreds of thousands of developers collaborate on the go. And we brought NPM to GitHub to support the largest developer ecosystem in the world.

This week, we announced four new features to help all software communities work together:

  1. Codespaces: Complete GitHub development environment that allows you to contribute immediately
  2. GitHub Discussions: New ways for software communities to collaborate outside of the code base
  3. Code Scanning and Secret Scanning: Help the community on GitHub generate and use more secure Code
  4. GitHub Private Instances: Collaboration is possible even for tightly regulated clients

To see ongoing discussions, browse the Satellite discussion.

Start coding quickly using Codespaces on GitHub

Note: Available in public beta

Contributing code to the community can be difficult. Each code base has its own way of configuring the development environment, which often takes dozens of steps before any code is written. Worse, sometimes the two development environments you are working on conflict with each other. Codespaces gives you a fully featured, cloud-hosted development environment that can be quickly launched directly on GitHub so you can immediately start contributing to the project.

Codespaces can load code and dependencies, developer tools, extensions, and point-files. Switching development environments is easy, you can do it instantly, and when you switch back it will automatically reopen the code space.

Codespaces, supported by Visual Studio technology, includes a full browser-based version of VS Code with support for Code completion and navigation, extensions, terminal access, and more. If you prefer a desktop IDE, you can launch the code space in GitHub and connect to it from your desktop.

Pricing for the code space has not yet been finalized. Code editing on GitHub will always be free, but if you use the Codespaces cloud environment, we plan to use a simple pay-as-you-go approach. In beta, Codespaces is free to use.

Learn more about Codespaces

Join the conversation through GitHub Discussions

Note: Public beta is coming soon

Software communities don’t just write code together. They brainstorm, discuss feature ideas, help new users find their way, and use the best ways to collaborate. So far, GitHub has only provided issues and PR as a place to talk. But issues and PR both have a feature that is great for merging code, but not for creating community repositories. Conversations need to have their own dedicated location, and that’s where GitHub Discussions come in.

Discussions exist in the project repository, so you can easily access them. It’s easy to start, respond, and organize unstructured conversations. In addition, questions can be marked as answered, so the community’s knowledge base grows naturally over time. And because discussions don’t close like issues, they can be used as a place to maintain FAQs and other collaborative documents. We realize that community discussion is as much a part of development as coding, so discussion contributions also appear in the user contribution graph.

We are testing with some of the open source community and will soon offer Discussions for other projects.

Explore the Satellite discussions

Protect the team’s Code with Code Scanning and Secret Scanning

Note: It is available in beta

Collaborating in the software community requires tools to help safely use and generate code. Last year, we announced the acquisition of Semmle, introduced code Security into GitHub developer workflows, made GitHub a CVE numbering authority, and launched GitHub Advanced Security products. Today, we are expanding our offerings with two new cloud beta versions:

Code scanning is now available on GitHub, and with Code scanning enabled, every Git push will be scanned for new potential security vulnerabilities and the results will be displayed directly in your PR. Code Scanning uses CodeQL, the world’s most advanced semantic analysis engine, which is excellent at finding vulnerabilities. We will provide free open source scanning to secure the world’s most important software. Any open source project can be registered.

Secret Scanning is now available for private warehouses. Since 2018, this feature (formerly known as Token Scanning) has been available in public warehouses. We’ve worked with many partners to expand our reach, including AWS, Azure, Google Cloud, NPM, Stripe and Twilio. Secret Scanning can now monitor known Secret formats in private repositories and notify developers immediately when they are found.

GitHub offers Code Scanning and Secret Scanning for free to all public repositories and as part of GitHub Advanced Security.

Sign up for beta features

GitHub Private Instances

Note: coming soon

Businesses rely on the GitHub community to build and use software, and we want every business to feel comfortable doing so, no matter how stringent their security and compliance requirements are. Today, we introduced plans for GitHub Private Instances, a new, fully managed option for enterprise customers. Private Instances provide enhanced security, compliance, and policy capabilities, including BYOK encryption, backup archiving, and compliance with regional data sovereignty claims.

Continue to explore

Watch the GitHub Satellite Keynote, which includes all the announcements and meetings from over 50 speakers from around the world on security, DevOps, collaboration, and more.

Watch making Satellite

That’s what GitHub did in its Satellite launch this year. If there is any improper translation, please correct it in the comments section.