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-co-commit

v1.1.0

Published

Git pairing with multiple co-authors in a simple way.

Downloads

8

Readme

Git co commit GitHub license npm Known Vulnerabilities

Documentation Get started

When a pair or multiple developers work on git projects, there is a convention that allows us to document our co-authors in the commit message. However, adding the co-authorship information on every single commit is painful.

Do a git commit in the same way it is usually done, with the pair members username, to make them get credit for the commit (if more than one member works on the same code, separate the username by comma). The author’s name(who writes the code - Driver) on the commit will be added automatically.

Each co-author will be added to the commit message, so that they are also credited in the github contributions view!

Before pairing

before pairing

After pairing

after pairing

Overview

  1. To install git co commit run the following command in the cmd or bash
$ npm i -g git-co-commit

It will install the git-co-commit package and add all the dependencies to the root level of your computer. To use the installed git co commit package do the following

  1. Create a folder and then open the folder in cmd or bash
$ mkdir demo
$ cd demo
  1. Run git init
$ git init
  1. Add index.html file
$ touch index.html
  1. Run git add index.html
$ git add index.html
  1. Run commit - it will ask for a commit message, once you add your commit message, it will ask for the pair’s username separated by comma (Author’s name doesn’t need to be included, it will be automatically added).
$ commit

Use git co commit

To know more visit the documentation site of git co commit

License

Git co commit is open source npm package licensed as MIT.