You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might make sense to figure how to have some sort of async communication method. I wonder if something could be created like a Google sheet that updates periodically to pull in new PRs. Then one of you could add notes (like "Last checked XXX date", "Pinged author", or "Needs CLA help"), and when the next person checks, they could act on any of the notes, and skip PRs that had been recently checked.
We would need the requests pulled into the sheet and updated on a regular cadence, if possible to allow us to track our triaging and not duplicate efforts.
The text was updated successfully, but these errors were encountered:
I could also use a similar data pull for a question I have (that I could not properly answer in Grimoire), of "which repos have community PRs and no CCs?"
Hi Ed - this is to look into possibly having a spreadsheet that pulls in the OSPRs that need review (that Tim and I will triage). This would be based on the sheet you created that pulled this info in, the sheet I created to do my initial run-through of the maintainer PRs, and Sarina's suggestion copied here:
It might make sense to figure how to have some sort of async communication method. I wonder if something could be created like a Google sheet that updates periodically to pull in new PRs. Then one of you could add notes (like "Last checked XXX date", "Pinged author", or "Needs CLA help"), and when the next person checks, they could act on any of the notes, and skip PRs that had been recently checked.
We would need the requests pulled into the sheet and updated on a regular cadence, if possible to allow us to track our triaging and not duplicate efforts.
The text was updated successfully, but these errors were encountered: