G2

Emrah L.

Wordpress Developer

Small-Business (50 or fewer emp.)

6/23/2026

"Great for simple issues, but struggles with complex tasks, speed, and request limits"

2.5/5

What do you like best about GitHub Copilot?

What I like most is that I can talk to Copilot directly from GitHub and have it immediately start working on issues. I assign it an issue, describe what I need in plain English, and it spins up a branch, makes the changes, and opens a PR for me to review—all without me ever leaving GitHub.

It’s genuinely changed how I handle my backlog. The small things I used to put off—dependency bumps, quick refactors, adding tests, or fixing minor bugs—would just sit there for weeks. Now I assign those to Copilot and stay focused on the harder problems. By the time I circle back, there’s usually a PR waiting for me to review and merge.

One thing I didn’t expect is that it’s pushed me to write better issues. Copilot clearly works best when the task is well scoped, so I’ve gotten into the habit of writing issues more carefully, which also helps me think the work through. And since everything still happens through normal issues and PRs, nothing gets merged without me signing off. It fits neatly into the way I already work. Review collected by and hosted on G2.com.

What do you dislike about GitHub Copilot?

What I dislike most is how quickly the quality drops once a task becomes even slightly complex. For well-scoped, self-contained issues it’s great, but as soon as something spans multiple parts of the codebase or requires real architectural judgment, the PRs it opens often miss the mark. I end up spending more time correcting them than I would have spent just doing the work myself.

The agent can also be slow. Waiting for it to spin up, work through an issue, and open a PR sometimes takes long enough that I’ve already context-switched to something else. Instead of helping, that delay breaks my flow.

It also burns through requests quickly on the more capable models, so I find myself rationing premium model usage and thinking about cost in a way that becomes distracting. And every now and then it confidently does the wrong thing—like ignoring an existing pattern in my repo or reformatting files it shouldn’t have touched—so I never fully trust a PR without reviewing every line. Review collected by and hosted on G2.com.

What problems is GitHub Copilot solving and how is that benefiting you?

The biggest problem it solves for me is the backlog of small, well-defined tasks that never felt worth carving out a dedicated block of time for, even though they still added up. Dependency bumps, minor refactors, adding test coverage, fixing straightforward bugs—things that used to sit untouched for weeks—now get a solid first draft while I stay focused on the harder work. I assign the issue, Copilot opens a PR, and I review it when I’m ready.

It’s also reduced the cost of context switching. Instead of stopping what I’m doing to handle a quick fix, I hand it off and keep my attention on the bigger problem, then come back to a PR that’s ready for review. That’s helped me stay in a deeper flow on the work that actually needs my attention.

And because it works through normal issues and PRs, it fits into how I already work rather than forcing a new tool or process on me. Everything stays in GitHub, nothing merges without my sign-off, and as a nice side effect it’s pushed me to write clearer, better-scoped issues—which has made my overall workflow feel more deliberate Review collected by and hosted on G2.com.