This month, we have some exciting updates to share. Many of you welcomed the improvements we made to your ability to sync forked repo and upstream from the web user interface, add video to questions and pull requests, and use custom notifications to mute noise — among other things.
What’s big in June?
Building software can be complex and challenging, but your management tools shouldn’t be. That’s why we’ve redesigned how Issues work in the new GitHub Issues, which is now available in beta. We introduced a number of features that allow you to create improved relationships between multiple questions when using the question task list, switch between project boards and spreadsheet-like tables, and add custom fields.
document.createElement(‘video’); Lot. Blog/wp – the content /…
This month, we’re also rolling out a tech preview of GitHub Copilot, a new AI-paired programmer that can help you write better code. GitHub Copilot extracts context from the code you’re working on, suggesting entire lines or functions. Check out the GitHub Copilot page for examples and faQs.
Literally, everything we ship
Making action
GitHub Discussion integration is now available on GitHub Actions. You can trigger an action workflow when a Discussion or DiscusSION_COMMENT event occurs. Please visit the documentation for implementation details and contact us if you have feedback.
The GitHub Action environment allows you to create environments with custom protection rules and secrets that you can refer to for your workflow tasks. See the Changelog entry for more details.
Making a desktop
GitHub Desktop 2.9 extends the drag-and-drop feature introduced in Desktop 2.7. You can now squish and reorder submissions, start a new branch from an earlier submission, and modify your last submission. If you’re using an Apple Silicon machine with the new M1 chip, Desktop 2.9 also upgrades you to a native build to improve performance and reduce crashes. Check out the blog post for more details on this release.
You can now suppress and reorder submissions on GitHub Desktop
Making enterprise edition
GitHub Enterprise Server 3.1 is now fully available. This version includes.
- GitHub Actions Workflow Visualization (#88) : Track and troubleshoot complex workflows at a glance.
- Auto merge Pull request (#107) : Automatically merge pull request when it is ready.
- Warehouse performance Optimization (#108) : For large, busy warehouses.
See the release notes for full details.
The general situation
Does your organization use an IP permit list to restrict access to its assets? We have made some changes so that your installation access token will now respect your organization’s allowed IP address configuration.
Making the problem
To tie in with the new GitHub Issues revamp, we’ve made some quality of life improvements, including the introduction of question forms so that maintainers can create structured forms with required fields that easily capture all the important details.
Structured forms make it easier to execute required fields
We also introduced a new status icon to quickly distinguish between your question and the status of the pull request.
The status icon (on the left) makes it easier to distinguish your questions or pull requests at a glance
Making packages
GitHub Packages container registry,ghcr.ioThe now widely available container registry provides the best developer experience for publishing, managing, and using containers on GitHub. For more information, check it outGeneral availability of the container registry blog.
Making the warehouse
New tools for discovering and resolving pull request conversations are now widely available. You can now find the comment on your pull request in the “File Changes” TAB of your pull request. You can also request that all pull request conversations be resolved before merging. For details on how to configure your Settings, see our documentation.
You can now request that all pull request conversations be resolved before merging
We now display a confirmation dialog box when the team requesting a review has more than 100 members. Take a look at the new feature below.
Lot release
You can use emojis nowCelebrate the new release!
we
Making security
We released a number of security updates in June, including new code-scanning capabilities. You can do a free text search of your code scan alerts to find specific alerts even if you don’t remember their names. You can also control which alerts cause pull request checks to fail by setting the severity.
Maybe you use CodeQL for code scanning? Great, we have more updates! It is now easier to analyze multiple languages on third-party CI/CD systems using CodeQL CLI. The latest CLI versions support the creation of multilingual CodeQL databases in a single command. This makes it easier to run code scan analysis if you are using a CI/CD system outside of GitHub Actions. (See the Changelog entry for information on how to use this new option.) But wait, there’s more! CodeQL code scanning now includes testing support for C++20. Note that currently, CodeQL can only create CodeQL databases for C++20 code built with GCC on Linux. The C++20 module is not supported. We also improved the code scan API to return the version of CodeQL queries for analysis. This can be used to reproduce the results or to confirm that the analysis is using the latest query. Finally, CodeQL scanning now generates diagnostic information for all supported languages.
Alas.
We also released several Dependabot updates in June. Dependabot Security and version updates now support PIP 21.1.2, Pip-Tools 6.1.0, and PIP V 2021-05-29. Dependabot version update now also supports Terraform 1.0, as well as support for locked files, vendors and private registries. Finally, we changed the way we schedule Dependabot updates: Each repository is assigned a random time at which all updates to the repository begin. This makes your updates faster and avoids heavy usage spikes. For details on how to customize a specific update time, see the Changelog entry.
There are also some security updates.
- Secret scanning now supports user-defined patterns for private repositories. If you use GitHub Advanced Security, you can specify custom modes for secret scans of private repositories. When a new schema is specified, a secret scan searches the repository’s entire Git history for it, as well as any new commits. Check out our documentation for more information on custom schemas and secret scans.
- RubyGems, Adobe, and OpenAI are now GitHub’s secret scan integrators. GitHub scans every exposed RubyGems, Adobe, and OpenAI API key submitted to the public repository. Any keys we find are forwarded to the relevant service, which automatically disables them and notifies the owner.
- Security alert notifications can now be opt-in. You will only receive your concerns and choose to receive them
All Activity, or you are configured to includeSecurity alertsSecurity notifications for the repository.
Making the theme
After introducing the Dark and Dim theme, we show you a dark high-contrast theme, now available as a public beta to all Github.com users. Choose to join the beta by enabling the theme in your Feature Preview Settings, which are located in the drop-down menu of the Profile menu. Once feature preview is enabled, browse the “Look” page in your profile Settings and select the dark high contrast theme.
You can enable dark high contrast themes through your profile Settings.
Check out our public roadmap to learn what’s coming up, follow GitHub Changelog on Twitter, and check out another review on the GitHub blog next month.