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

github-commit

v1.0.0

Published

commit a single file to a Github repository

Downloads

2

Readme

github-commit

commit a single file to a Github repository (suitable for automation)

installation

npm install github-commit
  • You need to have git available on PATH.
  • This module uses HTTPS to clone, so you don't need ssh on PATH.
  • You need a GITHUB_TOKEN with repo permissions (get it here).

configuration

Sample execution:

ghc_branch='feature/some-branch' \
ghc_content='some text to commit' \
ghc_path='public/features.json' \
ghc_repo='owner/repository' \
ghc_token='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' \
ghc_user='deploy-bot' \
ghc_email='[email protected]' \
npx github-commit

Configuration is done with rc. Keys are:

{
  "branch:" "feature/some-branch",  // branch to commit to
  "content:" "some text to commit", // by default this is Date.now()
  "path:" "public/features.json",   // repo's relative path to commit "content"
  "repo:" "owner/repository",       // Github repository
  "timeout:" 10000,                 // Command line timeout (10000 ms if blank)
  "message:" "some message",        // Commit message (auto generated if blank)
  "token:" "< GITHUB_TOKEN >",      // Your "Github Personal Access" token
  "user:" "deploy-bot",             // User to commit with
  "email:" "[email protected]", // email to commit with
}

Note that token, user, and email must belong to the same Github account. content is commited to path in the repository. It's equivalent to executing:

echo $content > $repo/$path

logs

You can enable logs by having DEBUG=github-commit in your environment variables.