Repository Badges

badges-_summary.md

Please see repository-type specific Gists for examples.

• All repositories should have Bug, Backlog and Active (In Progress) labels via Waffle.io to hep quickly grasp state of repository.
• Code Quality and Climate badge should be done via either Scrutinizer (PHP) or CodeClimate (JavaScript), depending on which works better.
• Gemnasium should be used to determine status of dependencies - it works with Composer, NPM and others.
• CircleCI should be used in most cases, keep in mind an API token is required for each repository and must be generated in CircleCI settings. This should demonstrate if the code in the repository actually works.
• For certain repositories custom badges (NPM, Packagist, etc.) may be used as well, when applicable.

badges-javascript.md

JavaScript Library (lib-js-elastic-filter)

Uses for front-end (non-node.js libraries)

---

---

---

badges-node-module.md

Node Module (object-settings)

Any Node modules, should have an NPM badge, if published to NPM.

---

---

---

badges-php-library.md

PHP Library (wp-amd)

This could be a WordPress plugin as well, the major distinction is PHP libraries should be listen on Packagist and will generally not have any Visual Regression tests.

---

---

---

badges-site.md

---


---

---

badges-wordpress-product.md

WordPress Theme / Plugin (wp-splash)

These types of repositories must have CircleCI monitoring and will ultimatly all include some sort of Visual Regression tests which will determine build status.

---

---

---