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

change-git-config

v1.0.4

Published

Rewrite your git config in existing repositories' history

Downloads

8

Readme

Change Git Config

npm version Dependabot Status

Did you change your email address? Got a new name? You can change those outdated git configurations across all of your repos at once, and make the remote repositories (e.g. GitHub) reflect those changes!

This is an upgrade over the previous PHP-based solution in that a. it doesn't mess up your commit history (uses git stash instead), b. it pushes across all branches (unlike before, which only pushed master), and c. the logging is less cluttered and easier to pinpoint what went wrong where (especially during force pushes).

Installation

Clone this repository.

Usage

  1. Run yarn start
  2. Specify a directory. Anything from ~/Projects, /Users/home/$project, to ./blah flies!
  3. Provide the outdated git information you'd like to update (i.e. your previous git config)
  4. Check that the new git information looks right
  5. (Optional) enable force push
  6. ???
  7. Profit!

Warning

Only enable force push with repos that you own or repos where you know the others will be okay with this change!

If your git is set to use a non-English language (e.g. Korean),

git(fullPath).checkIsRepo()

can go apeshit for some reason. In that case, try

echo 'export LANG="en_US" # for git' >> ~/.bash_profile

Additionally, the git configurations are case-sensitive, meaning that [email protected] and [email protected] look the same to git.

Testing

You can do a simple integration test (unfortunately interactive in some parts, but a lot of it is still automated) as follows:

  • yarn setup
    • Provide your GitHub credentials, and modify scripts/setup.sh with your GitHub username
  • yarn start:
    • Use the following credentials:
      • dir: ./sample
      • old name: your current git name
      • old email: your current git email
      • new name: something different from your current git name
      • new email: something different from your current git email
    • Afterwards, you should see the changes reflected on the github repo
  • yarn teardown
    • Provide your GitHub credentials, and modify scripts/teardown.sh with your GitHub username