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

wp-continuous-deployment

v1.7.2

Published

Continuous-Deployment for WordPress plugins with GitHub actions

Downloads

74

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ahmadawaisahmadawais

Keywords

wp-continuous-deploymentAhmad Awaisahmadawais

Readme

WP Continuous Deployment

DOWNLOADS Learn VSCode Follow @MrAhmadAwais on Twitter

DevOps free Continuous-Deployment pipeline for WordPress plugins with GitHub Actions.

📟

Install

npx wp-continuous-deployment

⚙️

Usage

❯ BEFORE

  1. Make sure your plugin is on WordPress.org
  2. Put your WordPress plugin on GitHub
  3. Clone the GitHub repo in your PC and browse it with command line
  4. Run npx wp-console-deployment in the root directory of the cloned GitHub repo
npx wp-continuous-deployment

❯ ONE-TIME SETUP

  • Follow the instructions, set the slug of your plugin which is the last part of the URL, e.g., for my plugin wordpress.org/plugins/cf7-customizer/ the slug is cf7-customizer
  • Add you WordPress.org SVN username/password (it's the same credentials you use for login.WordPress.org) in your plugin's GitHub repository settings.
  • Go to https://github.com/owner/repo/settings/secrets make sure to change the owner/repo part.

secrets

❯ AFTER

  1. All your plugin assets must have been downloaded in the .wordpress-org directory
  2. Now for each commit/push to master your assets & readme will get deployed (provided there are no other files modified. If other files are changed the build will be canceled)
  3. And for each new tag/push, a new version of the plugin will be deployed
  4. So, go ahead, make changes, git commit, and then run: git tag 2.0.0 && git push --tags — considering 2.0.0 is the new version

📝

Changelog

❯ Read the changelog here →

KEY: 📦 NEW, 👌 IMPROVE, 🐛 FIX, 📖 DOC, 🚀 RELEASE, and ✅ TEST

I use Emoji-log, you should try it and simplify your git commits.

📃

License & Conduct

🙌

Connect

👌

Sponsor

Me (Ahmad Awais) and my incredible wife (Maedah Batool) are two engineers who fell in love with open source and then with each other. You can read more about me here. If you or your company use any of my projects or like what I’m doing then consider backing me. I'm in this for the long run. An open-source developer advocate.

Or you can back me by checking out my super fun video course. As developers, we spend over 200 Hrs/month with our code editors — it's only fair to learn your next editor deeply. This course will save you 15-20 hours every month. Become a VSCode Power User →

VSCODE

VSCode Ahmad on Twitter