Starting today, we are enabling administrators to bypass all protection rules on a given environment (break glass) and force the pending jobs referencing the environment to proceed.
For more information, visit Using environments for deployment.
Today's Changelog brings you roadmap markers and command line support for Projects!
Keep track of upcoming dates in your roadmap by visualizing the due dates of your milestones, iteration durations and breaks, and additional date fields as vertical markers. Configure these from the Markers
menu to display them on the view.
Interact with projects, items, and fields from your favorite terminal with the GitHub CLI projects
extension.
To install the extension in gh
:
$ gh extension install github/gh-projects
Usage:
$ gh projects -h
Work with GitHub Projects. Note that the token you are using must have 'project' scope, which is not set by default. You can verify your token scope by running 'gh auth status' and add the project scope by running 'gh auth refresh -s project'.
Usage:
projects [command]
Available Commands:
close Close a project
copy Copy a project
create Create a project
delete Delete a project
edit Edit a project
field-create Create a field in a project
field-delete Delete a field in a project
field-list List the fields in a project
help Help about any command
item-add Add a pull request or an issue to a project
item-archive Archive an item in a project
item-create Create a draft issue item in a project
item-delete Delete an item from a project
item-edit Edit a draft issue in a project
item-list List the items in a project
list List the projects for a user or organization
view View a project
Flags:
-h, --help help for projects
Use "projects [command] --help" for more information about a command.
Share your feedback in the repository.
Learn more about extensions (and how to build your own!) in this GitHub blog.
/
in the name couldn't be duplicated (Enterprise users only)See how to use GitHub for project planning with GitHub Issues, check out what's on the roadmap, and learn more in the docs.
Starting today, we are enabling administrators to bypass all protection rules on a given environment (break glass) and force the pending jobs referencing the environment to proceed.
For more information, visit Using environments for deployment.
Code scanning default setup can now be easily enabled for a single repository from the slide-out panel on your organization's "Security Coverage" page, without needing to navigate to the repository's "Settings" tab.
The feature automatically detects the languages in your repository and enables analysis for pull requests and pushes, without requiring you to commit a workflow file. Default setup currently supports JavaScript, Python, and Ruby, with more languages to come. The feature is available for repositories using GitHub Actions and can be accessed by organization owners, repository administrators and security managers. Expect one-click enablement functionality for all organization repositories to be rolled out next.
This has shipped as a public beta to GitHub.com and will be available in GitHub Enterprise Server 3.9.
Learn more about automatically setting up code scanning for a repository and send us your feedback
Learn more about GitHub Advanced Security