In GitHub Desktop 3.1, we introduced viewing the diff of changes across multiple commits. This allows you to be certain there are no unintended changes in the group of commits you are about to push. Taking that feature to the next level, GitHub Desktop 3.2 allows you to Preview your Pull Request – see a diff of all the changes being introduced by your feature branch into your repository's default branch.
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-projectsUsage:
$ 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.
You can now enable secret scanning alerts on all your personal public repositories from your account's code security and analysis settings.
As before, you can also enable secret scanning alerts on any individual public repository or on all public repositories within an organization or cloud enterprise.
Secret scanning is free on public repositories, and available as part of GitHub Advanced Security on private repositories.
You can now view trending repositories across GitHub on your feed to discover more repositories of interest.
For questions or feedback, please visit our community.
GitHub Desktop 3.1.5 improves support for force pushing and fetching through the newly added Repository menu items as well as supporting pull request notifications on forks. This release also comes with many great contributions (12 changelog entries!
Previously, a user could only force push after an action such as rebasing. Now, when users find their branch in any diverged state, they can opt to use the force push Repository menu item. For example, a user can force push when commits exist on the remote that they are sure they want to overwrite.
Similarly, a user may find themselves in a new local branch they are not ready to publish, yet they want to fetch to see if there are any new changes on their main branch they would want to merge in. Instead of having to switch branches, they can use the Repository menu item to fetch those changes.
If you have been enjoying our Pull Request notifications on your repositories, you will be happy to hear that with 3.1.5 those same notifications are supported on forks.
We love the help we get from the open source community, providing many fixes and improvements for everyone to enjoy.
Thank you @angusdev for contributing all these fixes:
Thank you @tsvetilian-ty for adding support for JetBrains Toolbox and JetBrains Fleet editor for Windows.
Thank you @zipperer for adding support for emacs editor.
Thank you @patinthehat for adding support for JetBrains PhpStorm and WebStorm editors
Thank you @daniel-ciaglia for adding support for VSCodium as an external editor.
Thank you @Shivareddy-Aluri for adding the ability to copy tag names from the commit list.
Thank you @j-f1 for improving the the diff view by adding highlighting to Arduino's .ino files as C++ source.
Previously, only organizations with GitHub Advanced Security could enable secret scanning's user experience on their repositories. Now, any admin of a public repository on GitHub.com can detect leaked secrets in their repositories with GitHub secret scanning.
The new secret scanning user experience complements the secret scanning partner program, which alerts over 100 service providers if their tokens are exposed in public repositories. You can read more about this change and how secret scanning can protect your contributions in our blog post.
The npm CLI v9 is now generally available! As of today, running npm i -g npm will install the latest version (v9.1.1). Details on the major breaking changes, features and bug fixes of v9 can be found in our last changelog post.
A huge shout out to all of the contributors who helped make this release possible and who continue to make npm awesome.
Learn more about v9.1.1 in the release notes. You can also find references to previous releases in the project's CHANGELOG.md.
You can now enable Discussions for your organization, which is a place for your organization to share announcements and host conversations that aren't specific to a single repository within
your organization. To get started, go to Organization Settings -> Discussions -> Enable discussions for this organization.
For more information, see GitHub Discussions documentation.
For questions or feedback, visit GitHub Discussions feedback.
Polls are now available on GitHub Discussions! Polls make it easy for community members to gauge interest, vote, and interact with one another without having to comment. You can also start interacting with polls on our GitHub Mobile apps.
For more information, see GitHub Discussions documentation.
For questions or feedback, visit GitHub Discussions feedback.
We’re excited to introduce a new beta version of GitHub’s home feed on your dashboard,
designed to help developers build community, find inspiration, and celebrate each other’s incredible work.
To try it out, head to github.com and click "For you." For more information, see the documentation.
You can now view a preview of marked answers to discussions. Navigate quickly to the answer in a thread with the Jump to answer button.
For more information, see GitHub Discussions documentation.
For questions or feedback, visit GitHub Discussions feedback.
Get insights on your Discussions community with the new dashboard called Community in the Insights tab. This dashboard gives you a quick way to monitor the following:
For more information, see GitHub Discussions documentation.
For questions or feedback, visit GitHub Discussions feedback.
We've added enhanced support for CITATION.cff files to GitHub. CITATION.cff files are plain text files with human- and machine-readable citation information, and with this new feature, GitHub parses this information into convenient formats such as APA and BibTeX that can be copied by others.
Under the hood, we’re using the ruby-cff RubyGem to parse the contents of the CITATION.cff file and build a citation string that is then shown in the GitHub user interface. Special thanks to the gem creators @sdruskat @jspaaks and @hainesr who worked with us to build this.
Issues submitted to open source projects often lack important information. Markdown issue templates can help by providing text that contributors can remove and replace with their own input – but sometimes contributors can miss details or get confused.
New, YAML configured issue forms enable maintainers to build structured forms with required fields and easy-to-follow steps so that they can capture every important detail.
Issue forms are now available in beta for all publicly accessible repositories.