👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

@stevehipwell Unfortunately, I don't :/

• One option could be to create a custom linter for golangci-lint, but I don't know how involved that would be.
• Another that comes to mind, would be to create a Builder-pattern for repo and team resources, but that falls short quickly

One very simplistic check could be to run something like grep 'name\s+=\s+%s' -v *_test.go 😬

@deiga I was really thinking about keeping the PR valid before it's merged. Once it's in the code we'll just need to be good at reviewing. Custom linters are powerful, but the UX for contributors isn't great.

Ah, right. I was already thinking structural :D

@deiga if you get this ready to merge, we could look to get it prioritised so the burden lands on the new PRs (I know this pain from the tests PR)?

@deiga if you get this ready to merge, we could look to get it prioritised so the burden lands on the new PRs (I know this pain from the tests PR)?

I'll try get it tonight