Add script for checking the status of the backports#11065
Add script for checking the status of the backports#11065
Conversation
ccc8418 to
fa7a108
Compare
a128f36 to
1ec6521
Compare
…the other classes
It is on how many days since the PR was **updated**, not **created**, nor **merged**.
2f362c0 to
c7e6607
Compare
|
On the other hand, when running I came across: #9791 is already backported, but some reason is being marked as "to do". |
Mmmm that one is weird. I can confirm that the command that I'm using is As far as I know I try to not use Rails APIs, and if I use them I require them, as we're outside the Rails environment
I was just giving it one last look and found that one too. It's fixed on c11ce71
I think that's because the title was missing the "v" in "v0.26". The big assumption of this script is that the backports need to comply with the titles created with the "bin/backporter" script, so I can extract it all with the GitHub API. I guess I could have checked it with the git CLI too, but well, I went with this other approach as it was what we usually do manually to check if the backport was done or not. I fixed those titles and now it should appear as backported. |
Confirmed: |

🎩 What? Why?
This PR introduces a companion for the
bin/backporterscript. The idea is to be able to see which Pull Requests with thetype: fixlabel have backport PRs already created and related to them.Example command:
There's also a CSVReporter, that will allow us in the future to make a TUI or something like that that will allow us to use the output of this script as the input for the backporter script (see #9281)
📌 Related Issues
Testing
Run the script
./bin/backports_checker