GitHub today announced a bunch of new features at its virtual GitHub Universe conference including dark mode, auto-merge pull requests, and Enterprise Server 3.0.

GitHub has introduced draft pull requests to handle work-in-progress scenarios where you might want to open a PR or start a conversation with your teammates before your code is ready to be reviewed.

This is especially true for GitHub projects that have automated workflows setup to validate incoming Pull Requests via Actions.

This feature integrates with GitHub’s protected branches, Berman said — if the reviewer requested changes to a pull request on a protected branch, the pull request can be blocked.

GitHub Super Linter aims to automate the process of setting up your GitHub repositories so they will use the appropriate linter for your language whenever a pull request is created.

How to merge into master How does an average, everyday user of GitLab merge code into the master branch? The answer is to issue a GitLab pull request. A developer must log into the GitLab web ...

GitLab made collaboration and encouraging contribution a top priority, so they created the GitLab Merge Request to manage code discussions and code reviews prior to the code changes in a given branch ...

GitHub’s report of the incident also listed problems with things like pull requests, GitHub Pages, Copilot, and the GitHub API. Things seem to have escalated rapidly.

A GitHub project is an adaptable spreadsheet, task board, and road map that integrates with your issues and pull requests on GitHub to help you plan and track your work effectively.