You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, there's no way for us to reliably inform hosts that there is an update in the test runner.
Describe the solution you'd like
If there was a versioned Action publicly available on the GitHub Actions marketplace, hosts could configure dependabot alerts in their repositories that inform them that there are new versions available.
We currently have a workflow in this repository that allows the test reporter to be run within GitHub Actions. However, it assumes that you have a fork of this repository and keep it up to date with this upstream one. Publishing the action allows hosts to include the action within any repository, eliminating the need to maintain a separate one just to participate in this.
Describe alternatives you've considered
Alternatively, another workflow could be added to this repository that automatically pulls in any upstream changes into any fork on a regular basis.
Additional context
We don't currently release and tag versions for this repository. That would probably need to change in order to ensure specific versions of the action continue working. I'm not familiar with publishing actions to the marketplace, but that may require a separate repository.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, there's no way for us to reliably inform hosts that there is an update in the test runner.
Describe the solution you'd like
If there was a versioned Action publicly available on the GitHub Actions marketplace, hosts could configure dependabot alerts in their repositories that inform them that there are new versions available.
We currently have a workflow in this repository that allows the test reporter to be run within GitHub Actions. However, it assumes that you have a fork of this repository and keep it up to date with this upstream one. Publishing the action allows hosts to include the action within any repository, eliminating the need to maintain a separate one just to participate in this.
Describe alternatives you've considered
Alternatively, another workflow could be added to this repository that automatically pulls in any upstream changes into any fork on a regular basis.
Additional context
We don't currently release and tag versions for this repository. That would probably need to change in order to ensure specific versions of the action continue working. I'm not familiar with publishing actions to the marketplace, but that may require a separate repository.
The text was updated successfully, but these errors were encountered: