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

gitlogme

v1.3.2

Published

git --log your last month to a file

Downloads

15

Readme

gitlogme

Build Status

git log your last month work to a file. With class.

Installation

Make sure you have node and npm installed and run:

npm i -g gitlogme

Usage

For the sake of simplicity, config your git username and email if you haven't. Otherwise, you will have to provide --name or --email arguments.

Then simply:

  • cd your-awesome-project
  • gitlogme

Options

All options are... optional! gitlogme will try to find out these by itself.

| option | type | description | | --------------- | ------- | ---------------------------------------------------------- | | -n --name | String | Your git user | | -e --email | Email | Your git email | | -s --since | String | Date to log from, YYYY-MM-DD, default is 18th last month | | -u --until | String | Date to log to, YYYY-MM-DD, default is 18th current month | | -f --format | String | Git log format, default is %h%x09%an%x09%ad%x09%s | | -d --dest | Path | Where do you want to save the file, default is OS home dir | | -o --open | Boolean | Open the file upon creation | | -h --help | Boolean | Displays help menu |

Examples

So let's say you'd like to generate a log file with all your commits since 2014

gitlogme --since 2014

Or maybe you want to see your workmate's log

gitlogme --name Joe --since 2014

Contribute

Feel free to fill an issue, pull-request are preferred.

IMPORTANT: Always create feature branches from the beta branch.

Automated versioning

We use semantic-release to automate the versioning process, make sure you follow the commit message convention explained here.

HEADS UP: If you are not sure how write a commit message, make your changes in your feature branch and run npm run commit and follow the assistant.

Releases

Beta

Create a feature branch and make a pull-request to beta branch. Once its merged, you can try and install the package using @beta dist tag on npm.

> npm i -g gitlogme@beta

Production

Create a new pull-request from beta to master branch. Once it gets merged, the final version will be released using @latest dist tag on npm.