Read this project's settings

GET

/v1/settings

const url = 'https://beta-api.plune.ai/v1/settings';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://beta-api.plune.ai/v1/settings \
  --header 'Authorization: Bearer <token>'

No id in the path: routes are user-scoped and the project is the implicit default. A project that has never been configured reads as an empty object, never as absent.

Authorizations

bearerAuth
cookieAuth

Responses

200

The settings

application/json

Everything a project owner can configure. Two keys today; the shape makes room for the next without another table.

object

statusMapping

Per source, what each raw status means here. The source key is any string — a team on a runner nobody wrote defaults for can still say what its statuses mean.

object

key

additional properties

object

key

additional properties

string

Allowed values: passed failed broken blocked skipped

trustedDiscoverySources

Sources whose discovered tests become cases WITHOUT passing through the review queue. The permission is granted to the source, not to each test: a discovered test already exists in your repository, so approving it one page at a time is a formality that costs ceil(N/200) decisions. Listing a source here answers all of them at once, and every case it creates carries trusted-source as the reason in the audit log.

Array<string>

Example

{
  "statusMapping": {
    "additionalProperty": {
      "additionalProperty": "passed"
    }
  }
}