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

gitblind

v1.0.2

Published

Keep files in local git repositories that'll never be committed.

Downloads

5

Readme

gitblind

Version: 1.0.2

Author: FaizChishtie

Keep files in local git repositories that'll never be committed.

Why?

Sometimes you need to keep a file in your repository that you don't want to commit. For example, you might have a local.sh script file that you don't want to commit to your repository. You could add it to your .gitignore file, but that adds unnecessary clutter to that file. gitblind solves this problem by blinding files in your repository so that they'll never be committed.

How?

gitblind adds files or patterns you choose to blind to your local .git/info/exclude file. This file is not tracked by git, so it won't be committed to your repository.

Contents

Installation

You can install gitblind with npm:

npm install -g gitblind

You can also install it with yarn:

yarn global add gitblind

Usage

Blind a file

Blinding a file is as simple as running gitblind in the root of your repository:

gitblind .my-secret-file

You can also blind multiple files at once:

gitblind .my-secret-file .another-secret-file

You can also blind a directory:

gitblind /my-secret-directory

Blinding a directory will blind all files in that directory.

Blind a pattern

You can also blind a pattern:

gitblind *.sh

This will blind all files that end in .sh.

List all blinded files

You can list all blinded files by running gitblind with the ls command:

gitblind ls

Unblind a file

You can unblind a file by running gitblind with the rm command:

gitblind rm .my-secret-file

You can also unblind multiple files at once:

gitblind rm .my-secret-file .another-secret-file

You can also unblind a directory:

gitblind rm /my-secret-directory

Reset all blinded files

You can reset all blinded files by running gitblind with the reset command:

Note: You must use the -c flag to confirm that you want to reset all blinded files.

gitblind reset -c

This will remove all blinded files from your .git/info/exclude file.