{"id":88428,"date":"2025-06-05T09:00:00","date_gmt":"2025-06-05T16:00:00","guid":{"rendered":"https:\/\/github.blog\/?p=88428"},"modified":"2025-06-04T14:13:49","modified_gmt":"2025-06-04T21:13:49","slug":"how-to-create-issues-and-pull-requests-in-record-time-on-github","status":"publish","type":"post","link":"https:\/\/github.blog\/developer-skills\/github\/how-to-create-issues-and-pull-requests-in-record-time-on-github\/","title":{"rendered":"How to create issues and pull requests in record time on GitHub"},"content":{"rendered":"\n

Software development has always started with a conversation: What problem are we solving, why does it matter, and what does “finished” look like?<\/em><\/p>\n\n\n\n

On GitHub, that conversation crystallizes in an issue<\/strong>. No matter what tools you’re using or who you’re working with, a well-designed issue still sets the agenda for pull requests (PR), reviews, tests, and deploys.<\/p>\n\n\n\n

That principle hasn’t changed—but how we get from idea to issue to PR is changing fast, with Copilot helping to speed things up. By asking Copilot to draft an issue<\/strong><\/a>, you can quickly design a clear plan for moving forward. Then (and here’s the fun part) you can assign that issue directly to the new GitHub Copilot coding agent<\/a>, which will asynchronously work to execute on the task at hand and give you a PR. <\/p>\n\n\n\n

This is a new way of working. But the basic developer experience is simple, familiar and—dare I say—GitHubby<\/em>. <\/p>\n\n\n\n

In this blog, we’ll talk about:<\/p>\n\n\n\n