Skip to content

GitHub

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.

Grade D · dataset: API (the vendor’s response payloads) · type github

What it is

A GitHub repository. It is a repository, not a data source. In the test estate it is the EDI team’s issue tracker.

Grade

D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.

See the grade table for all 32 types.

Settings and credentials

From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.

Names
Typegithub
Settingsnone
Credentialspersonal_access_token

The test connection

EDI integrations repo

SettingTest value
(none)
owner (in Config.Extra)quillmere
repo (in Config.Extra)edi-integrations
api_url (in Config.Extra)https://github.quillmere.invalid/api/v3

Credentials: personal_access_token. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.

Stand up the test system

The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.

  1. Download github.zip and unzip it. It holds the vendor’s response payloads and expected.json.
  2. Any repository with a fine-grained personal access token will do for a live connection. The dataset’s issues are the quickstart estate’s EDI tracker.
  3. Open the payloads next to expected.json: every field the expected model names is in the payload, with the join keys described below.

What FACE finds

A repository, not a data source: the catalogue has no discovery for github, by design. The dataset is what the REST issues endpoint returns.

DatasetKindDomainPrimary keyRowsFields
issuesrest_resourceengineeringnumber37

expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.

How it joins the Quillmere universe

This source carries 1 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.

Universe entityFields hereAlso in
shipmentissues.bodybigquery, d365, databricks, document, excel, files, guidewire, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, salesforce, sap, servicenow, sharepoint, tms, whs, yms

Evidence it holds for the planted anomalies:

  • ANOM-4, A duplicate customer PO. github/repos_quillmere_edi-integrations_issues.json in github.zip, look for PO-0002-4194 (the EDI team’s own bug report).

See all connectors at once for the walkthrough across every source.

Download

This is one of 25 zips: the 7 streaming types ship as replay recordings instead.

What is in the zip
  • github/repos_quillmere_edi-integrations_issues.json
  • github/expected.json

The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.