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 seems this works on GitHub now. If we have PRs like #1971 where all we do is shuffle around files and imports, that stuff is useless in the blame view, so we can filter it out.
Tried in 1745a75 and reverted in e2e56d8. It did work to filter the git blame, but I realized that if there are any changes in the commit that you don't want to hide the blame for, you are in trouble. For example, with the most recent commit ignored, you can't tell from the blame when we added the ~/* alias in the tsconfig.
So if we want to use this feature in the future (and it is very cool) we need to make sure that the commits in question don't have any lines we want to be able to blame.
It seems this works on GitHub now. If we have PRs like #1971 where all we do is shuffle around files and imports, that stuff is useless in the blame view, so we can filter it out.
https://github.com/orgs/community/discussions/5033#discussioncomment-2318478
The text was updated successfully, but these errors were encountered: