https://github.com/carlthome/vscode-git-line-blame

Display inline information of the last commit that edited the currently selected line in the editor
https://github.com/carlthome/vscode-git-line-blame

git vscode vscode-extension

Last synced: 2 months ago
JSON representation

Display inline information of the last commit that edited the currently selected line in the editor

• Host: GitHub
• URL: https://github.com/carlthome/vscode-git-line-blame
• Owner: carlthome
• License: agpl-3.0
• Created: 2023-09-16T13:48:54.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-06-27T00:39:53.000Z (7 months ago)
• Last Synced: 2024-06-27T03:48:22.724Z (7 months ago)
• Topics: git, vscode, vscode-extension
• Language: TypeScript
• Homepage: https://marketplace.visualstudio.com/items?itemName=carlthome.git-line-blame
• Size: 204 KB
• Stars: 18
• Watchers: 2
• Forks: 4
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Git Line Blame

Visual Studio Code extension that displays inline information in the text editor about the latest commit that edited the currently selected line.

## Features

This extension is small on purpose and doesn't come with any settings. It will automatically activate when you open a workspace that contains a git repository. When you select a line in the text editor, the commit summary, author, and time elapsed since that commit edited that line will appear next to the line number in a discrete and unobtrusive color.

## Usage

Simply install the latest version from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=carlthome.git-line-blame). Releases are made from [GitHub Actions](https://github.com/carlthome/vscode-git-line-blame/releases).

## Develop

First, if you're new to VS Code extension development, skim through [CONTRIBUTING.md](./CONTRIBUTING.md) first.

## Set up local development environment

```sh

# Install package in the working directory.

npm install

# (Windows & MacOS) Run unit tests.

npm test

# (Linux) Prepend `npm test` with `xvfb-run -a` when running on Linux.

xvfb-run -a npm test

```

### Release a new version

1. Update and commit the `CHANGELOG.md` with the new version and changes according to [semver](https://semver.org/)

1. `npm version minor` (or `major` or `patch`)

1. `git push`

1. `git push --tags`

1. Submit a new release by `gh release create v$(npm pkg get version | xargs)` and fill in the details.

## FAQ

### Why not just use GitLens instead?

GitLens is an excellent extension but I found it overly complicated for my needs, with many features I didn't need. It's also frustrating that the extension keeps pushing for its paid version. In contrast, this extension will always be free and open source software (see [license](./LICENSE)), and will never do more than just provide the line blame information.

### What's that extension icon?

Created by prompting Stable Diffusion over in [stable-diffusion](https://github.com/carlthome/stable-diffusion) with `python main.py --prompt "git line blame"`. 🫢