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

alo-executor-github

v1.0.4

Published

Runnerty module: github executor

Downloads

13

Readme

Github executor for Runnerty:

Config

We can config it via user and password or via token:

{
  "id": "github_default",
  "type": "@runnerty-executor-github",
  "auth":{
    "token": "MY_TOKEN_HERE"
  }
}

or

{
  "id": "github_default",
  "type": "@runnerty-executor-github",
  "auth":{
    "username": "MY_USERNAME",
    "password": "MY_PASSWORD",
  }
}

Plan

  • List issues of a repository filtering by label and update date:
{
  "id": "github_default",
  "command": "listIssues",
  "user": "runnerty",
  "repo": "runnerty",
  "options": {
    "labels": "bug",
    "since": "2018-03-06T16:00:00Z"
  }
}

Options:

| Name | Type | Description | |---|---|---| | milestone | integer or string| If an integer is passed, it should refer to a milestone by its number field. If the string * is passed, issues with any milestone are accepted. If the string none is passed, issues without milestones are returned | | state | string | Indicates the state of the issues to return. Can be either open, closed, or all. Default: open | | assignee | string | Can be the name of a user. Pass in none for issues with no assigned user, and * for issues assigned to any user.| | creator | string | The user that created the issue. | | mentioned | string | A user that's mentioned in the issue. | | labels | string | A list of comma separated label names. Example: bug,ui,@high | | sort | string | string What to sort results by. Can be either created, updated, comments. Default: created | | direction | string | The direction of the sort. Can be either asc or desc. Default: desc | | since | string | Only issues updated at or after this time are returned. This is a timestamp in ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ. |