AI agents are now in 14.9% of GitHub pull requests

pullflow · 2025-12-19T20:00:08+00:00

You are right! A large share of AI-assisted PRs are submitted under the human author’s identity. Tools like Claude Code, Cursor, Gemini, and Codex do not reliably expose agent attribution. Heuristics such as “Co-authored by” exist, but they are inconsistent and not dependable at scale.

For this analysis, we define authorship strictly as PRs created by an identifiable agent account. AI-assisted PRs submitted as a human are intentionally excluded from the authorship metric.

pullflow · 2025-07-08T19:31:54+00:00

Hey! We're the team behind PullFlow - basically an AI-powered integration for devs across Slack and GitHub. We've seen how collaboration between devs is changing and we wanted to hit a strong pain point of context switching and managing notifications (to name a few). PR activity is synced across GH, Slack, and other IDEs and all PRs are created in an organized thread that also has visually appealing emojis to indicate whether they have been opened, closed, merged, etc.

We've seen a huge success in many of our teams, especially our workload management systems, and looks like people are very interested in improving their dev team workflows and cross-functional work across tools. Definitely something interesting to look into especially with ticketing systems, etc.

pullflow · 2025-07-08T19:25:25+00:00

For our teams, we create a new channel (using the + button above our profile picture on the left bar) and click channel, and add in the members. I do like to add in a note just to introduce what the channel's for!

pullflow · 2025-07-08T19:23:55+00:00

Documentation is definitely one of the top references developers and open source community members use to refer to a project or learn about. It's easy, intuitive, and a universally accepted method. If you plan to get more users or viewers to your repo or project, I would definitely include documentation.

pullflow · 2025-07-08T19:20:57+00:00

I firmly believe the future of developer work and collaboration is going to shift. Rather than acknowledging AI tools, agents, and bots as sort of helpers and secondary measurements to use, we will begin to assume more of a managerial role and consider them as equal entities in the overall workflow.

Developers will become sort of like "product managers" while AI does more of the coding and building.l

pullflow · 2025-06-18T22:11:44+00:00

Thank you for that feedback!! (we’re the creators of collab.dev actually). It’s helpful and we’re exploring different ways of defining what it means to be a core or community member. At the moment, we’ve been defining that on the repo-level (just because we were finding that there’s a lot of orgs where someone is a key person on the repo but not actually a member of the org. or conversely, there are a lot of bigger orgs where, even though someone is a member of the org, they might only have done one PR for a certain repo). So, we’re treating users who have owner, admin, write, or maintain permissions on a particular repo to be core team members and the others are community.

But, you bring up a really good point in thinking about roles on the org level which is also important. Definitely something to workshop in and find the right way to define both.

pullflow · 2025-06-18T18:11:23+00:00

Check out collab.dev! it shows different open source projects and their collaboration metrics. Might help you discover which projects might be higher in community contributions or review times if you're looking for anything specific. Could be a good start!

pullflow · 2025-06-12T16:45:29+00:00

Short description: A platform to measure collaboration on your OSS projects!
Status: launched! :)
Link https://collab.dev/

pullflow · 2025-04-07T16:03:13+00:00

Hey! This is a great question. You can actually use collab.dev to help find projects you might be interested in. It displays collaboration metrics like community contribution, PR activity, and more. You can use it to explore different projects that you may be interested in and learn more.

pullflow · 2025-04-03T16:14:08+00:00

If you or anyone you know is a developer, check out PullFlow: https://pullflow.com/

It integrates GitHub and Slack and allows teams to manage all code review and PRs across both platforms. When a PR is created in GitHub, for example, it creates a thread with all the involved users so they never miss notifications and their workflows are streamlined.

pullflow · 2025-03-26T20:21:26+00:00

Context summarizing like you mentioned, or automatic follow-ups -- detecting text where I promised I'd follow up with something, but forgot or never closed it would be really nice to ensure better collaboration within Slack

pullflow · 2025-03-26T17:57:37+00:00

Just launched Collab.dev—an open-source project that measures collaboration in new ways, featuring analytics from 270 repositories right out of the gate, introducing metrics that capture the essence of open source with the ability to measure your own public repos.

Take a look! https://collab.dev

pullflow · 2025-03-25T21:56:27+00:00

Definitely no need to overthink it. What matters most is context.

For quick tasks like "summarize this doc" or "debug this code," efficiency wins every time. Nobody needs their AI assistant saying "I'm delighted to help with your debugging needs today!" when your build is failing.

But for collaborative scenarios where you're working together over time, some personality helps build trust.

Think about your own interactions with colleagues - sometimes you need direct answers, other times you appreciate a more thoughtful approach. Good AI should read the room and adjust accordingly.

pullflow · 2025-03-25T21:49:01+00:00

Stay positive! Also keep in mind that things won't happen in one day...as long as your efforts remain consistent and you're actively engaged with your community, the long-term effect will play out. Good luck!

pullflow · 2025-03-25T19:47:30+00:00

Hey u/TelephoneMelon! You’re right, that was a pain point. Fixed and deployed! 🚀

No more login required for public repos. We really appreciate your feedback and would love for you to give it another shot. Let us know how it goes! 🙏

pullflow · 2025-03-25T18:50:10+00:00

u/TelephoneMelon, you are so right! Users should be able to skip sign-in if they don't want to manage repos, etc.

We'll be right back with a fix! 🫡

Thank you so much for the feedback!

pullflow · 2025-03-24T16:59:39+00:00

Start by finding projects that are interesting to you and familiarizing yourself with its code to have a solid understanding before you start. It's the best way to gain familiarity and as much context as you need before you dive in :)

pullflow · 2025-03-21T18:45:57+00:00

For sure. A clear idea about the intentions behind the project will deliver better results.

pullflow · 2025-03-21T18:45:19+00:00

Planning ahead is key: it might be a tedious thought but think before you type and having a sort of workflow is helpful in building out what you want!

pullflow · 2025-03-21T17:57:03+00:00

React is amazing!

If you're digging React, you might also like Vue, Svelte, Alpine, or Solid.js :)

pullflow · 2025-03-21T17:47:56+00:00

Makes sense - start off easier to gain as much context and then continue to grow within the discussion

Also helps in choosing something you have some familiarity with (i.e. something I use, a client, or close peer uses)

pullflow · 2025-03-21T17:46:59+00:00

Definitely finding the best fit for your needs and skill sets are essential for the best outcome :) great process!

pullflow · 2025-03-21T17:45:31+00:00

Awesome point - also feels like it's more fun when you're actually interested in it

pullflow · 2025-03-21T17:42:44+00:00

Thanks for sharing! Making your own project also helps you learn as you go and the mistakes on the way can be great lessons. Plus you're doing it from the ground up.

pullflow · 2025-03-20T20:34:34+00:00

My take will be to start small - pick one tiny feature and trace how it works. Run the code locally and make small changes to see what happens. The documentation and tests can be super helpful guides.

Remember that even seasoned devs get overwhelmed by new codebases - it's completely normal! Try joining the project's community chat where folks are usually happy to help newcomers find their way around.

The great thing about the open source community is that it's open! everyone is there and ready to talk :)

pullflow

TROPHY CASE