You can now set the Title, Label, and Assignees of an Issue in the Issue template.

https://help.github.com/enterprise/2.16/user/articles/creating-issue-templates-for-your-repository/

Issues can now be deleted.

• User who can delete
• For repositories owned by an organization, a user with admin privileges for the organization and a user with admin privileges for that repository
• If the repository is owned by an individual user, that user
• You can delete the issue from "Delete issue" at the bottom right of the issue screen.

https://help.github.com/enterprise/2.16/user/articles/allowing-people-to-delete-issues-in-your-organization/

Setting method

• For organization-owned repositories
• Go to https://[hostname]/organizations/[owner]/settings/member_privileges.
• Check "Issue deletion" at the bottom of the screen and press "Save" at the bottom.
• This setting can only be done by users with Organization owner privileges.
• Personal user-owned repositories can delete issues by default.

It is now possible to hide file deletion diffs in the pull request diff display.

• In Files changed of Pull request, press “Fils filter...” and press “Hide deleted files” to hide the difference of file deletion.

https://help.github.com/enterprise/2.16/user/articles/filtering-files-in-a-pull-request-by-file-type/

If a review is required to merge a pull request, and if the review is approved, the screen will switch so that the merge button can be pressed if the pull request screen is open.

• In Files changed in the pull request, press ”Fils filter...” and check only the extensions to be displayed.

Image Diff now shows each file size when viewing a "2-up" comparison.

https://help.github.com/en/enterprise/2.16/user/articles/rendering-and-diffing-images

You can now create or upload files after creating an empty repository.

• “creating a new file”
• “uploading an existing file”

When you press the "Fork" button again in a repository that has already been forked, a list of repositories that have been forked so far will be displayed.

Web notifications can now be saved.

• 1. Go to https://[hostname]/notifications.
• 2.notification right sidePress to save the notification to "Saved for later".
• 3. Click on the right side of the saved notification.You can unsave the notification by pressing .

https://help.github.com/enterprise/2.16/user/articles/saving-notifications-for-later/

Added "In this user" option when using the search Box at the top of the screen from the user profile page.

• This searches the target user's own repository, files within that repository, and the wiki.
• In the following case, the repository owned by the logged-in user will be searched.

You can now specify release values using query parameters when creating a new release.

• Determine the release value by appending the following query parameters to the URL for creating a new release (https://[hostname]/[owner]/[repo]/releases/new).
• Tag version: tag=[tag-version]
• Target branch: target=[target-branch]
• Title: title=[title]vvv
• Description: body=[release description]
• Prerelease: prerelease=1
• Example: Tag=v1.0.1, Title=version1.0.1, Description=New Feature Added https://172.25.55.16/test-org/test-repo/releases/new?tag=v1.0.1&title=version1.0.1&body = Added new features.

* You can also specify target branch and pre-release.

https://help.github.com/enterprise/2.16/user/articles/automation-for-release-forms-with-query-parameters/

Users with organization owner privileges can now restrict the types of repositories that organization members can create.

Setting method

Go to https://[hostname]/organizations/[owner]/settings/member_privileges.
From Repository creation in the center of the screen, select the type of repository that can be created, and press "Save" at the bottom.

about choices

Public and private repositories You can create Public and private repositories.
Only Private repositoriesPrivate repositories can be created.
Cannot create new Disabledrepository.

https://help.github.com/enterprise/2.16/user/articles/restricting-repository-creation-in-your-organization/

Collaborators invited to repositories owned by an organization can be restricted from all users to users within the organization.

Setting method

Go to https://[hostname]/organizations/[owner]/settings/member_privileges.
By unchecking the Repository invitations in the center of the screen and pressing "Save" at the bottom, you can limit invitations to users within your organization.
Users who have already been invited will not have their permissions changed even if the checkbox is unchecked, and will be able to access the repository in the same way as before the setting was changed.

https://help.github.com/enterprise/2.16/user/articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories/

When the history is rewritten by force push, it is now recorded in the timeline event.

https://help.github.com/enterprise/2.16/user/articles/restricting-repository-creation-in-your-organization/