prisma-risk / tsoracle / 26254183524
95%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 49
Run time 1min
Badge
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
coverage: 93.961%. Remained the same
26254183524

push

github

web-flow 
ci(release-plz): use a dedicated app token so PRs trigger CI (#52)

* ci(release-plz): use a dedicated app token so PRs trigger CI

The default `GITHUB_TOKEN` was creating release-plz's PR but its push
events do not trigger downstream workflows (GitHub's anti-loop policy
for the default token). That made every release-plz PR start with no
CI, requiring a manual close+reopen to kick off ci.yml.

Mint a short-lived installation token from a tsoracle-dedicated GitHub
App before each release-plz step and pass it as `GITHUB_TOKEN`. Pushes
and PRs created under the App's identity propagate as user-style
events, so ci.yml runs automatically. Also pass the token to
`actions/checkout` so any direct git operations in the workflow use
the same identity.

The App is scoped to this repository only — keeps the credential
isolated from the org's private repos.

Prerequisites for this to work (documented inline in the workflow):
  1. Create a GitHub App with `Contents: Read+Write` and
     `Pull requests: Read+Write`; install it on `prisma-risk/tsoracle`
     only.
  2. Add repo-level secrets `RELEASE_PLZ_APP_ID` (numeric ID) and
     `RELEASE_PLZ_APP_PRIVATE_KEY` (full PEM).

* ci(release-plz): drop inline prerequisite comments

The PR body already documents what needs to exist (the dedicated app and
the two repo secrets); leaving the same text in the workflow file just
makes the steps harder to skim once the setup is done.

5695 of 6061 relevant lines covered (93.96%)

93330.79 hits per line

Jobs
ID Job ID Ran Files Coverage
1 26254183524.1 49
93.96
 GitHub Action Run
Source Files on build 26254183524