Badgen.net: Support Cirrus CI

[tunnckoCore]

https://cirrus-ci.org/guide/writing-tasks/#embedded-badges

But not sure for the states. Also not sure which projects uses it so to use for examples.

I'm consider switching to it in near future. The only thing that stopping me currently is environment variables handling, which i highly depend on for my full automation of auto-release, auto-update and auto-publish flow.

The cool thing about CircleCi is that it allows you to have one "global store" of environment variables, so you set it once and every old and new project you setup you can access it.

It's quite slow to do that for each project. Add cirrus config file, go to cirrus dashboard add env to that specific repo and etc. All that was one of the reason i switched from travis.

So yea, Cirrus CI is amazing and fast, but. :D

[amio]

Much faster than CircleCI? For me I prefer Travis for it's super handy setup, .travis.yml and that's all.

[tunnckoCore]

It's always that way ;d And if you dont have full automation and dont do much packages per day. When you dont want to go to settings for every single project to add tokens (or run semantic-release-cli locally), then it is not so easy.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tunnckoCore]

Nooooooooooo :laughing: :rocket: