Skip to content

Conversation

nzaytsev
Copy link
Contributor

@nzaytsev nzaytsev commented Jul 24, 2024

Description

Screen.Recording.2024-07-24.at.13.58.51.mov

Checklist

  • I have followed the guidelines in the Contributing document
  • My changes follow the coding style of this project
  • My changes build without any errors or warnings
  • My changes have been formatted and linted
  • My changes include any required corresponding changes to the documentation (including CHANGELOG.md and README.md)
  • My changes have been rebased and squashed to the minimal number (typically 1) of relevant commits
  • My changes have a descriptive commit message with a short title, including a Fixes $XXX - or Closes #XXX - prefix to auto-close the issue that your PR addresses

@nzaytsev nzaytsev linked an issue Jul 24, 2024 that may be closed by this pull request
@nzaytsev nzaytsev requested review from d13 and eamodio July 24, 2024 06:59
@nzaytsev nzaytsev force-pushed the feature/2980-first-name-for-inline-blame branch from c015c64 to 760009f Compare July 25, 2024 03:23
@nzaytsev nzaytsev force-pushed the feature/2980-first-name-for-inline-blame branch from 760009f to 7da3bbd Compare September 9, 2024 09:45
@nzaytsev nzaytsev force-pushed the feature/2980-first-name-for-inline-blame branch from 9266ad2 to 2cdbed2 Compare September 9, 2024 09:50
@eamodio
Copy link
Member

eamodio commented Sep 25, 2024

Closing in favor of b31b09c

@eamodio eamodio closed this Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

First name for inline blame?

2 participants