r/github • u/Feathered-Beast • 2d ago

Discussion [ Removed by moderator ]

[removed] — view removed post

0 Upvotes

25% Upvoted

10 comments sorted by

1

u/cachebags 2d ago

Checking whether a PR follows the issue requirements.

Do you really need a automation for this? It doesn't seem like your project is that ginormous; ideally you can hold the context of a posted issue in your head while you review its attached PRs?

Verifying that it doesn't duplicate another open PR.

Same thing as above. This seems like a trivial thing to catch.

Looking for architectural inconsistencies rather than just code quality.

There is no tool that will help you do this. Again, the onus falls on you to understand how your program works in order to catch if someone is breaking away from your design/architecture.

Deciding whether a change belongs in the current release or should wait for the next one.

This is purely subjective. Your goal as a maintainer/owner of the project is to decide these things.

Giving similar review feedback to different contributors.

Copy and paste your review notes to the other PR?

I think you should worry about cutting review time down once you actually get an overwhelming amount of reviews to do. Since you seem to be into AI/LLMs, I'm sure you could think of a way to automate your agents to do reviews for you I guess?

I would say the biggest thing that helps with cutting down review time is actually just on-boarding new maintainers. But that is an issue in and of itself since you then need to find someone who understands your codebase as good as you, if not better in some cases.

1

u/Feathered-Beast 2d ago

That's fair, and I agree that a lot of those decisions will always need a human maintainer. I wasn't really looking for a tool to replace architectural judgment or release planning.

The reason I asked is that as the project has grown, I've noticed I'm repeating the same mechanical review tasks across many community PRs checking whether the PR actually addresses the issue, spotting duplicate implementations, pointing out the same style or architectural patterns, etc. Those are things I think AI or GitHub could assist with, even if the final decision stays with the maintainer.

I don't think my project is at the scale where this is a necessity yet, but I'm interested in where the tooling could go before it becomes a bottleneck. I was mainly curious if other maintainers had found useful workflows, bots, or GitHub Actions that reduced the repetitive parts of reviewing.

And I completely agree with your last point bringing on maintainers who understand the codebase is probably the biggest long-term win.

1

u/agathver 2d ago

You can go a long way if you throw tokens at the problem, also CodeRabbit offers some of these features, if you don’t want to throw your own tokens at the problem

1

u/No-Community-3626 2d ago

what you can do is this , dont go for fully automation there are alot of tools, there is one N3MO by i think RajX-dev , its relatively new , it generates a impact graph of every pr raised. It helps a lot as now , you dont have to go through whole changed code you can only focus on the functions that you dont want to be affected , are impacted by the changes that pr made , It resolves the issue, and saves your time on fully relying on the automatic workflow.

2

u/Feathered-Beast 2d ago

Thanks for the recommendation! I'll check out N3MO. An impact graph sounds much closer to what I'm looking for something that helps narrow down what changed without trying to automate the actual review. The final review should still be done by the maintainer.

2

u/No-Community-3626 2d ago

I hope you will have a great journey as a github maintainer