chore: get commits for testing #9050
Conversation
|
Build successful! 🎉 |
|
Build successful! 🎉 |
yihuiliao
changed the title
There was a problem hiding this comment.
I'm getting Please verify that your date is correctly formatted when running node scripts/getCommitsForTesting.js 2025-10-07 2025-10-18, but then it continues to run properly.
Also it might be cool for the default to the last week if no arguments are provided.
There was a problem hiding this comment.
Maybe it would be best to have it pull all the commits for now until we get into the habit of tagging stuff with "needs testing"? Wonder if the PRs that shouldn't be tested are in the minority and thus easier to scan through from a full list rather than tag every PR that needs testing
| @@ -0,0 +1,164 @@ | |||
| const Octokit = require('@octokit/rest'); | |||
There was a problem hiding this comment.
would be nice if we had a bot account with limited perms so we could avoid having to have everyone auth via cmd line. Ideally stored in secrets somewhere but maybe more trouble than it is worth unless we make an automated job to do this?
|
Build successful! 🎉 |
4 participants
This doesn't completely automate testing sheets but it just gathers a list of commits between two dates, that way you don't have to keep going back and forth between tabs to get the url for each commit. Then it writes it to a csv file which you can copy and then paste into a Google Sheets.
If we start using labels more, it'd be possible to sort them by RAC, V3, S2. Right now, it's just searching for keywords to categorize them but not every commit has these keywords.
In order for the commits to be pulled, the PRs need to marked with the "needs testing" label, that way we don't get every single PR.
It will use the info under "Test Instructions" in the PR description to fill out the instructions for the sheet. If the instructions are over 350 characters, it'll just say "go to pr". Now an actual reason (jk) to fill out this section!
✅ Pull Request Checklist:
📝 Test Instructions:
run
node scripts/getCommitsForTesting.js 2025-10-07 2025-10-18. you should new file created called 'output.csv'.copy the results from 'output.csv' into google sheets. with everything highlighted, go to Data at the top, find "split text to columns", and then make sure you have separate by commas selected.
just make sure to get rid of output.csv when you're done
🧢 Your Project: