Big news for computer science (CS) teachers. GitHub verified teachers using GitHub Classroom get access to GitHub’s groundbreaking, browser-based IDE, Codespaces. It’s a seismic shift for CS education, breaking down barriers in a fundamentally new way. Whether you’re a teacher frustrated with the complexities of managing local machine-based developer environments, tired of troubleshooting your students’ tools rather than focusing on their code, or looking to reduce technical and cost barriers for your CS Classroom, Codespaces addresses so many of the pain points in CS education with one elegant solution – integration in GitHub Classroom.
You can enable Codespaces in GitHub Classroom and then choose it as the preferred editor when creating assignments.
These changes will gradually roll out over the next week. For more information on how to use this new experience, check out our documentation and blog. Your feedback is welcome at our Education Community Forum.
With the latest update of GitHub Mobile, we're introducing more project fields on issues and pull requests! You can now edit custom text, number, date, and single-select fields for issues and pull requests that belong to the new projects experience from within the triage sheet.
Read more about GitHub Mobile and send us your feedback to help us improve.
Now, admins can block creation of branches that match a configured name pattern. For example, if a repository's default branch is renamed from master to main, admins can prevent any subsequent creation or push of the master branch so that only the new branch name is used.
Previously, admins could use branch protection rules to restrict who could push to existing branches, but they couldn't block the creation of those branches. This is now possible using a branch protection setting named Restrict pushes that create matching branches. To use the setting, create a new branch protection rule with a name pattern that matches the branch name you want to block (e.g. master or not-allowed*). Then, enable the settings Restrict who can push to matching branches and Restrict pushes that create matching branches, as shown here:
For more information, visit About protected branches in the GitHub documentation.
We appreciate feedback on this and other topics in GitHub's public feedback discussions.