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
As a user it is discouraging to see dead badges on the README.md, and can result in the notion that this is not a maintained repo.
Either you need to expose the pipeline fly -t <target> ep -p <pipeline name> or we need to remove the badges from the file. We do need a pipeline, so if concourse is not running or no longer desired we should change it to the community standard with is normally travis CI.
Our tests on windows however will stop work unless appveyer has a free tier for open source. That needs to be investigated
The text was updated successfully, but these errors were encountered:
From the lack of feedback I take it that I need to set up a travis pipeline? So I will do that in the near future.. I need access to the AWS bucket however to store the artifacts
As a user it is discouraging to see dead badges on the README.md, and can result in the notion that this is not a maintained repo.
Either you need to expose the pipeline
fly -t <target> ep -p <pipeline name>
or we need to remove the badges from the file. We do need a pipeline, so if concourse is not running or no longer desired we should change it to the community standard with is normally travis CI.Our tests on windows however will stop work unless appveyer has a free tier for open source. That needs to be investigated
The text was updated successfully, but these errors were encountered: