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

force-push-to-protected-gitlab-branch

v0.3.0

Published

This simple helper will remove the protected status from your current gitlab branch, push, then immediately restore it.

Downloads

21

Readme

force-push-to-protected-gitlab-branch

Usage

npx force-push-to-protected-gitlab-branch

or

npm install --global force-push-to-protected-gitlab-branch
force-push-to-protected-gitlab-branch

Instructions

This simple helper will remove the protected status from your current gitlab branch, push, then immediately restore it. You will need to provide your private gitlab access token in one of 3 ways:

  • interactively
  • by providing PRIVATE_ACCESS_TOKEN=xxx environment variable
  • by configuring it in the settings file (see settings.example.json for example file structure).

Settings file location is:

  • $HOME/.force-push-to-protected-gitlab-branch-settings.json, if using with npx
  • settings.json in the root of this project, if using with npm install --global

If you paste the env interactively, you will be prompted to save it at the correct location, so that's the recommended workflow.

If your current branch isn't protected, we will abort. To push anyway and then protect it, call with the --force flag.

Dev

There are intentionally no dependencies. Just clone and dev.

Licence

MIT