Repo Settings ChrisRega/json-diff

GENERAL

  • Repo Token
    v8f4lnuyqUp5uJplTGoScUyWnoz5RhAQo regenerate
  • Readme Badge

    Add a badge to your README.md file to show your coverage status.

    Embed ▾
    README BADGES
    x

    If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

    Markdown

    Textile

    RDoc

    HTML

    Rst

  • Recache

    Recache the coverage for each branch of this repo.

    recache
  • Resync

    Resync the location, privacy setting, and default branch of this repo with your SCM.

    Resync
  • Repo needs a new owner

    Claim the repo so your Github API token is used for source files.

    Claim
  • Admin info
    Created by /github/ChrisRega/json-diff/settings

    30 May 19:52
    7 builds.
    7 processed jobs.

LOOK AND FEEL

  • Layout Type

    default: "builds" contain "jobs" | monorepo: "builds" contain "subprojects"

COVERAGE

  • Include branch coverage?

    Include branch coverage in aggregate coverage calculations.
    (If it's present in your coverage reports.)

  • Include Vendor Directory Coverage?

    Include files in /vendor directory in coverage calculations.
    (Legacy setting for Ruby projects only.)

PULL REQUESTS

  • Leave PR comments?

    Send coverage reports as pull request comments.

  • Format:

    compact: one-line comment | detailed: multi-line comment with all details

STATUS UPDATES / CHECKS

  • Send status updates?

    Send commit statuses (aka. status updates) to your SCM.

  • Limit status updates to overall build?

    Don't send a status update for each individual job or subproject.
    (Only applies for parallel builds.)

  • Coverage Threshold for failure

    The minimum coverage required for a build to pass.
    (Turns status updates into pass/fail status checks.)

    %
  • Coverage Decrease Threshold for failure

    The maximum decrease allowed before a build is failed.
    (Turns status updates into pass/fail status checks.)

    %
  • Send patch status updates?

    Send status updates for patches (the new code in pull requests).
    (Only applies for pull request builds.)

  • Patch Coverage Threshold for failure

    The minimum coverage required for a patch to pass.
    (Only applies for pull request builds.)

    %
  • Use (pull request) context for pull request builds?

    Use coverage/coveralls (pull_request) instead of coverage/coveralls
    (Only applies for pull request builds.)

  • Include coverage % with warnings about drifted builds?

    Drifted pull request builds can have inaccurate coverage reports.
    Include (potentially inaccurate) coverage details in status updates for drifted builds.
    (Only applies for pull request builds.) More info





Delete Repository

Deleting the repository removes all data from Coveralls.io and this action cannot be undone.

Delete Repo

Are you sure you want to delete this repo?

This cannot be undone. Removing this repo will also destroy any past historical data

Type json-diff to confirm