This renames `npm run test:server` to `npm run test:core` to go along with the reorganization of #2698. `server` has been a bit imprecise, since there's a lot of stuff under test besides the server, and most of the tests don't hit the server itself.
Probably files like `luarocks.spec.js` ought to be run as part of a different target, especially if we build out a separate code-coverage metric for core. Though I'm not in a huge rush to sort that out.
The intention of wrapping HTML in an `__html` is to avoid accidentally unsafe rendering of something that is non-html.
Including this in the definition export solves the problem, and does not seem too onerous for other possible users of that file.
Close#2725
* fix: updated Azure DevOps fetch function to reflect query param name change
* fix: fixed branch filter for azure devops to enable branch name usage
* fix: simplified branch pattern for azure devops badges
It’s happened twice that `[*]` has ended up in a PR title and the full test run has happened inadvertently. Once was me and once was a new contributor.
This raises the bar on doing it accidentally.
Numeric colors weren't properly being handled by `makeBadge` after #2742.
Since this function really does not need to be accepting colors as strings, rather than make the function more lenient to work with Scoutcamp, I coerced the types of the colors on the way in.
Two tests cover the functionality in the modern service. I don't feel strongly that the legacy version needs coverage at this point, though I've added one for the moment on the github languages badge where this manifested.
Fix#2778
* Fix orange statuses
* Add test for partially succeeded build
* Add service test for partially succeeded builds
* Add service test for partially succeeded builds
- Replace the idea of color schemes with the idea of named colors (since none of our colorschemes have used `colorA`)
- Pass through the normalized color to `_shields_test` to harmonize with BaseService and simplify testing
- Update service tests
- Move responsibility for color generation into the npm package
- Remove several color helper functions and their tests
- Update gh-badge public API to accept `color` and `labelColor`
This is a precursor to refactoring some of the logo code for #2473.
It's easy to push services that don't validate, because much of the tooling, including the service test runner and the service definition generator, do not validate all the services. This leads to errors that manifest in CI. It would be more helpful to see these errors sooner.
This moves the `validateDefinition()` check to `loadServiceClasses()`, where the services are first loaded, and fixes related validation errors.
Two of these regexes have triggered a LGTM alert.
https://lgtm.com/rules/1505904457770/
I’m not terribly concerned about it given this is a test, though it’s nice to clear these up, and the new regexes are a bit easier to understand.
* New Service: Bitbucket Server: Pull Request Count
* [Bitbucket]: Pull Requests: Add Support for bitbucket-server
* Update examples to use namedParams instead of exampleUrl
* Simplify cloud vs server check
* [Bitbucket]: Add support for bitbucket cloud private repos
* Add additional tests for bitbucket server
* [Bitbucket]: Add tests for basic auth
* [Bitbucket] Format secrets according to style guides
* [Bitbucket] Add link to server REST documentation
* Punt adding VSCode debug task to separate PR
* [Bitbucket] Remove extra truthy check on serverSecrets
* [Bitbucket] Fix credentials after rename
* [Bitbucket] Use query parameters for Bitbucket Server support
* Fix bitbucket creds in secret template
* [Bitbucket] staticExample -> staticPreview
* Remove VSCode specific gitignore entries
* [Bitbucket] Normalize pluralization of PullReqeust(s) to match file name
