With templates for Issues and Pull Requests, administrators can help their team add the right details at the start of a thread.
You can add an Issue or Pull Request template by creating a new file in the root directory. Markdown support makes it easy to add things like headings, links, @-mentions, and task lists to your templates. Learn how to create a template.
You can now use pre-receive hooks to enforce organization-wide push policies—such as audit requirements—and optimize your team's workflows before any code lands on GitHub.
You can add pre-receive hooks in your account's admin center. For more details on creating, adding, and managing a pre-receive hook environment, read our documentation.
With GitHub Enterprise 2.6, administrators have greater flexibility over their Protected Branches the options to merge out-of-date pull requests and set restrictions on which users and teams can merge branches.
GitHub Enterprise 2.4 launched Protected Branches. You can also use the API to help maintain a project’s conventions at scale. Learn how to configure Protected Branches.
You can now drag and drop files into repositories, so team members who are not familiar with the command line can share files directly with developers.
Your team can now write expressively in comments without learning markdown. We’ve introduced text formatting across GitHub to do some of the work for you and help you learn.
Instead of replying with a string of +1 comments, your team can streamline their conversations and choose from a range of emoji reactions to add to any comment or Issue.
You can now create saved replies to save you time and keep your most popular responses on hand. You can thank the GitHub community and this Chrome Extension for this feature.
Effective code review catches bugs and improves code consistency. Now there are more ways to review pull requests on GitHub. You can filter files by extension, see new changes since your last visit, and more.
Merge commits lets you see your commmit history in detail, but often not all commits are created equal. Squash merging lets developers organize their Git history into a tidy, easy-to-digest history.