Rename/consistency for CIs - Circle, Travis, AppVeyor
See original GitHub issueFor consistency, i think it would be good all of the CIs to be build | passing
or build | success
, or every CI to have label its name, or every CI badge to be same, except icons
- CircleCI or
- TravisCI or
- AppVeyorCI or
Always dreamed about that 😆
Would be awesoome if they include icons by default and be build | passing
.
Hm. What about “icon style” at icon.badgen.net
? So all badges will have their respective icons (if they have). How cool is that (btw, should add white icons too ;d)
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Appveyor vs CircleCI vs Travis CI | What are the differences?
Appveyor - Continuous Integration and Deployment service for busy Windows developers. CircleCI - Automate your development process quickly, ...
Read more >AppVeyor: Continuous Integration and Deployment service for ...
CI/CD service for Windows, Linux and macOS. Build, test, deploy your apps faster, on any platform. Create your FREE account now. Interested in...
Read more >Adding `[circle skip]` to commit message to skip
I sometime use multiple CIs to cover different platforms (Travis CI for Mac and AppVeyor for Windows). Occasionally, I want to make a...
Read more >Continuous Integration Travis & Appveyor - GitHub
An audio server, programming language, and IDE for sound synthesis and algorithmic composition. - Continuous Integration Travis & Appveyor ...
Read more >Coveralls Currently Supports These CIs
service_name: travis-pro repo_token: ... GITHUB CI. View docs here. CIRCLE, JENKINS, SEMAPHORE AND CODESHIP. When using these CI's you must either ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Default icon Better let user to choose if they want icon within. We could provide icon examples in the index page, hinting user to use it freely.
Status consistency Nice to have, we need to count all possible status from all 3 CI(and more will comming), to know for sure if this consistency works flawlessly.
Non-white icon I’m planning modify every non-white icon to white 😄 We don’t provide ‘social-style’ badge, no need for those non-white icons.
Text padding Sharp eyes! 👍 Need more tweaks on badgen 😋
I prefer to leave status text to provider’s choice, that would be best suit their definition of status. A CI could do more than just building, the ‘passing’ may not suit for future use cases, even it looks OK for circleci + travis + appveyor for now.