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 🙏

© 2025 – Pkg Stats / Ryan Hefner

artifacts-url-comments

v1.4.8

Published

Add comments with artifacts urls to pull request or associated issues

Downloads

4

Readme

When

This action is to be used with a workflow run for a pull request event or push event with the pull number in the commit message ( matches on #pullnumber) The action can also be used with a repository dispatch of a pull request or push workflow run see. In this case you need to set the input workflowPayload.

Behaviour

Will create comment/s in pull request and / or associated issues containing the url to artifacts from the workflow run being watched.

Inputs

pull request event only

pullState is used to restrict the pull requests returned and defaults to open. Change to all or closed as necessary

Error behaviour

The default behaviour is to fail when there are no artifacts - control this with errorNoArtifacts.

There will be an error if there is no pull request found. Set continue-on-error: true in your workflow if the error is to be ignored.

Comment control

Comments can be created in the pull request and / or associated issues - control with addTo.

The comment that is generated can have a prefix and a suffix.

It is possible to filter out artifacts from comments by using the artifact name.

This is a accomplished with either includes or includesFormatted. The latter being used if the formatting of the artifacts is not consistent.

If includes is not provided then all artifacts are included.
If you provide then e.g - name1, name2

If using includesFormatted then - array of objects {name:string,format?:string}

Formatting

There are 3 formats

The default, url, will just have the url of the artifact in the comment.

Name will result in [name](url)

The final format is custom and is a format string e.g Whatever ({name})[{url}] etc

Related issues

The remaining inputs control the discovery of the pull request associated issues.

There are 4 ways that associated issues can be specified.

Common

All 4 use the inputs closeWords and caseSensitive as part of their matching.

Close words defaults to the close words used by github to automatically close an issue from a pull request.

Pull request and commits

In the pull request itself - control with usePullTitle and usePullBody.

In the pull request commits - control with useCommitMessages.

The pull request title, pull request body and commit messages will match against closeWord #123

Branch name

Control with useBranch, branchIssueWords and branchDelimiters.

The branch name will match closeWord delimiter branchIssueWord delimiter issuenumber e.g - fix-issue-123

Example workflow yaml

name: add artifact links to pull request and related issues
on:
  workflow_run:
    workflows: [Pull request or push run that uploads artifacts]
    types: [completed]

jobs:
  artifacts-url-comments:
    name: add artifact links to pull request and related issues job
    runs-on: windows-2019
    steps:
      - name: add artifact links to pull request and related issues step
        uses: tonyhallett/[email protected]
        env:
            GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
            prefix: Here are the artifacts 
            suffix: Have a nice day.
            format: name
            addTo: pullandissues