npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

gitreview

v1.1.0

Published

Review topic branch commits by files changed

Downloads

7

Readme

gitreview

gitreview -- Summarize files changed in current topic branch

gitreview is a wrapper around this git command:

$ git log --oneline --reverse --name-only master..HEAD

I use this command when considering whether to squash any commits before submitting a pull request to merge the topic branch into master. Rather than remembering the whole command, I defined this alias in my .gitconfig:

[alias]
    review = log --oneline --reverse --name-only master..HEAD

gitreview produces listings like this:

64f00c8a  title of first commit in topic branch
    path/to/file/changed/a
e2d395b1  title of second commit in topic branch
    path/to/file/changed/b
    path/to/file/changed/c
23de746f  title of second commit in topic branch
    path/to/file/changed/b

path/to/file/changed/b
    e2d395b1
    23de746f

The gitreview wrapper enhances the output of git review in two ways:

  1. It bolds each commit line (not shown above), and indents each file path, making the listing easier to read.
  2. It records for each file the commits in which the file changed, and then appends the inverted listing, listing the files that where changed in two or more commits. In the above example, only one file was changed in multiple commits, so the inverted listing inluded only the commits in which path/to/file/changed/b was changed.

NOTES

  1. gitreview assumes by default that your topic branch was created as a branch from master. If you created the branch from some other branch or commitish you should specify that branch with the --branch option.
  2. gitreview explicitly requests git log to abbreviate commit hashes to a specified length, defaulting to 8. This is done by using the --abbrev option to git log.

USAGE

  Usage: gitreview [options]

  Summarize files changed in current topic branch

  Options:

    -h, --help                output usage information
    -b, --branch [commitish]  The commitish the topic branch was created from [master]
    -a, --abbrev [digits]     Abbreviate commit hashes to the number of digits [8])