There's no blame specifically for that line, there's only a big blame block. However if you follow the PR's link, (5 clicks and 4 page loads later) you'll end up on this page:
This feature would need I think:
Step 2 should (if possible) verify that the linked PR is effectively the one that was squashed, and not just a randomly-linked PR.
I dont think we should load it on blame.
Rather allow the user to click alt and then load
{
repository(owner: "sindresorhus", name: "refined-github") {
object(expression: "ad17f062d53fa911c131ce1be964e1d20d5e6f72") {
... on Commit {
associatedPullRequests(last: 1) {
nodes {
mergeCommit {
oid
}
commits(last: 1) {
nodes {
commit {
oid
}
}
}
}
}
}
}
}
}
const pullRequests = select.all('[data-hovercard-type="pull_request"]')
for (const pullRequest of pullRequests) {
console.log(pullRequest.nextElementSibling.href.split('/')[6])
}
And redirect to that commit
Side Note: @Github we changed the clock...

Rather allow the user to click alt and then load
Yeah that鈥檚 what I said, only after the user clicks on it because it requires a specific query per commit
Rather allow the user to click alt and then load
Yeah that鈥檚 what I said, only after the user clicks on it because it requires a specific query per commit
Alt click?
Then redirect to blame of last commit of the pr
Step 2 should (if possible) verify that the linked PR is effectively the one that was squashed, and not just a randomly-linked PR.
I was thinking to take the commit and get the associated pr with it
I added to the query the merge commit that we can compare it