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

prify

v1.0.1

Published

Breakdown commits into individual Pull Requests

Downloads

2

Readme

prify

Break down each individual commits from a branch into individual Pull requests

Install

npm install -g prify

Prerequisites

  • A gitub token with repo perimissions stored into GITHUB_TOKEN environment variable

Usage

prify break down each individual commits from a branch individual Pull requests. This let you create simpler pull requests that people can review.

Here is a typical workflow, when working on large feature

1/ Create a functional branch.

This will be the only branch where you add commits. prify will take care of cherry-picking commits from this branch into individual commits branches.

git checkout -b "important-stuff"

2/ Append a bunch of commits

git commit -a -m "add abc"
git commit -a -m "add xyz"

3/ Cleanup commits

Eventually if things get messy during devloment make a soft reset to reorganise your branch into a list of reviewable commits.

git reset --soft <merge-base>
git commit ...

3/ pullrequestify

Execute prify.

prify

This will

  • Create a feature branch feature-important-stuff
  • Create a branch foreach commit important-stuff-1-of-n, important-stuff-2-of-n, ...
  • Open your browser so you can edit each pull request using feature-important-stuff as the base branch.

4/ Address PR-reviews

Once you start getting some reviews, you can simply use fixup to fix your commits, and execute prify again to update your commits branches

git commit --fixup <commit 1>
git commit --fixup <commit 2>
prify

This will

  • Cherry pick fixup into your commits branches
  • Open previously created pull-request in your browser.

License

MIT