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

@richicoder1/jenkins-github-helpers

v1.4.0

Published

jenkins-github-helpers CLI

Downloads

5

Readme

jenkins-github-helpers CLI

A CLI for jenkins-github-helpers.

Commands

Comment

Adding a comment to a PR:

npx -p @richicoder1/jenkins-github-helpers jgh comment --body "Hello World!"

Options are:

| Flag | Description | | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | --body <string> | The body of the comment. Either --body or --bodyFile is required. | | --bodyFile <fileName> | A file containing the body of the comment. Either --body or --bodyFile is required. | | --deleteBodyFile | If this flag is specified, jgh will delete the specified bodyFile after it has run. | | --once [key] | Specify this to only post a comment to a PR once. If a key is specified, it use that as a unique id. Otherwise it uses the comment body. |

NOTE: This command assumes the presence of a GH_TOKEN that has permissions to add comments to a link. It also assumes the presense of either a CHANGE_URL, or a GIT_URL formatted as an https git link and a CHANGE_ID. The former should be provided in a standard jenkins environment.

Files Changed

Helper command for detecting if a glob of files has changed

npx -p @richicoder1/jenkins-github-helpers jgh changed src/**

with a return result of 0 meaning a match was found, and a return result of 1 meaning no matches were found.

Alternatively, if you want to parse the output and consume it from javascript, you can pass the --json flag.

npx -p @richicoder1/jenkins-github-helpers jgh changed package* --json

The output would look something like:

success

{
	"error": false,
	"result": { "matched": ["package-lock.json", "package.json"] }
}

failure

{"error":false,"result":{"matched":[]}}}

error

{ "error": true, "message": "something bad happened" }

Flags

| Flag | Description | | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | --json | Output results to stdout as json. Always returns 0. | | --verbose | Outputs the changed files in addition the the matched files. In --json mode, this means there will be a changed array in the result. |

NOTE: This command assumes the presence of GIT_COMMIT and the very least. This, however, only gets the changed files for the current commit. To get the full set of changes since a previous build, you should also provide one of GIT_PREVIOUS_SUCCESSFUL_COMMIT, GIT_PREVIOUS_COMMIT, or CHANGE_TARGET.

License

MIT - see LICENSE