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

git-commit-standup

v0.1.4

Published

Always prepared for a standup: what did I do yesterday, what is my goal for today, and do I have any blockers?

Downloads

1

Readme

git-commit-standup

Hard to remember yesterday when it's standup time. Always be prepared with > standup

Photo by Paolo Nicolello on Unsplash

Install

yarn global add git-commit-standup

# or with npm

npm install -g git-commit-standup

Basic usage

$ standup --authors [email protected]

~/repos/frontend
d25b960 #9 Support --since thismonth|lastmonth
d12f92e #7 Support repositories key in config file
7c5da83 #7 Add support for multiple repos

~/repos/backend
964bd3f #7 Add typing to report output
4f589ee #7 Add ability to filter by author
99817d0 #8 Read and use config from ~/.timesheetrc
fa2889a #8 Add type for HomeDirectoryConfig
fdda89c #8 Add code to read json config from home directory

The script will automatically assume a 5 day workweek, Monday - Friday. If the script is run on Monday, it will show any commits since Friday (last 72 hours). Otherwise, it'll show commits from the last 24 hours.

Clean commit messages is obviously an advantage.

Options

Usage: standup [options]

Options:
  -V, --version                         output the version number
  -a, --authors [[email protected]]       Only care about commits from these
                                        emails.
  -s, --since [date]                    Analyze data since date (including).
                                        [today|lastweek|thismonth|yyyy-mm-dd]
                                        [default: lastworkday]
  -u, --until [date]                    Analyze data until date (excluding).
                                        [today|lastweek|thismonth|yyyy-mm-dd]
                                        [default: now]
  -r, --repositories [path,other-path]  Git repositories to analyze.
                                        [default: .]
  -e, --email [emailOther=emailMain]    Group person by email.
  -m, --merge-request [false|true]      Include merge requests into
                                        calculation.
                                        [default: true]
  -i, --ignore-standuprc                Ignores .standuprc from home
                                        directory.
                                        [default: false]
  -j, --json                            Reports in JSON format.
                                        [default: false]
  -v --verbose                          Prints extra stats
                                        [default: false]
  -D --debug                            Prints debug information
                                        [default: false]
  -h, --help                            display help for command

  Examples:

  - Show commits made last workday until today (author taken from git config)

   $ timesheet

  - Show commits from last workday by [email protected]

   $ timesheet -a [email protected]

Config

.standup config

By default, the repository parameter will check the current git repository. You can also summarize multiple repositories by adding a config file to your home folder.

The config has the following structure:

{
  "repositories": [
    "/Users/tomfa/repos/notes",
    "/Users/tomfa/repos/app",
    "/Users/tomfa/repos/backend"
  ],
  "authors": ["[email protected]"],
  "emailAliases": {
    "[email protected]": "[email protected]",
    "[email protected]": "[email protected]"
  }
}

The config above will look for commits in three different locations, made by [email protected], [email protected] and [email protected].

Roadmap

#1: Pulling down issue info from issue tracker

If you commit with references to an issue tracker, e.g. #1 my commit message, the script can connect and pull down information on those