MapColonies / shigola / 8783ec544
57%
master: 44%

LAST BUILD BRANCH: chore/drop-vendor
DEFAULT BRANCH: master
Ran
Jobs 1
Files 126
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: 55.662%. Remained the same
8783ec544

push

github

web-flow 
ci(release): open a release pull request with release-please (MAPCO-11502) (#28)

* ci(release): open a release pull request with release-please

Merging to the default branch now opens a release pull request carrying the
next version and the changelog entry for it, generated from the Conventional
Commits this project already writes. Merging that pull request tags and
publishes the release, which is the `release: published` event
on_release_publish.yml already builds and pushes from -- so release automation
ends where the existing publish workflow begins, and neither grew a copy of the
other's job.

Manifest mode rather than the one-line `release-type:` form, because three of
the decisions below have nowhere to live in the one-liner.

bootstrap-sha is cd2f2488, "Initial commit -- Shigola". It is exclusive, so the
first release's changelog starts at the first commit this fork made and stops
before a decade of upstream history it would otherwise read as unreleased. That
boundary already exists in the tree -- it is the merge base of every branch
here -- so this is not a new line drawn anywhere, and release-please ignores the
key once a release pull request has merged.

The manifest is empty: this repository has never released under its own name.
The versions in CHANGELOG.md are Tegola's, and claiming one of them as ours
would say this software is a continuation of that version line when it is
deliberately not a superset of it. An absent version is what makes the first
release an initial one, which is what initial-version 1.0.0 then answers. A
major is not a flourish: the fork removed the entire conventional tile surface,
so no 0.x number describes the step from Tegola honestly.

changelog-sections departs from release-please's defaults by surfacing refactor,
build and docs, which it hides. In this tree a refactor is routinely a removal
-- "retire the standard provider interface", "delete the go-side geometry
processing trees" -- and a first release whose... (continued)

5810 of 10438 relevant lines covered (55.66%)

122.86 hits per line

Jobs
ID Job ID Ran Files Coverage
1 8783ec544.1 126
55.66
GitHub Action Run
Source Files on build 8783ec544