Repository navigation
ci: use the quality-reports template of the quality dashboard - #49
Merged
Merged
Conversation
ESLint findings move to the unit-web job, which already has the npm dependencies. Test reports are uploaded even when tests fail, so the dashboard shows the failures. Duplication excludes test files through .jscpd.json.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the handwritten
quality-reportsjob with the template from simvia/common-tools/quality (templates/github-actions.yml), used by every repo on the quality dashboard (quality.simvia.internal).unit-webjob, which already installs the npm dependencies..jscpd.jsonexcludes test files from duplication (same 3.0% as before).The job only runs on
main, so its first artifact appears after merge.