synackd / ochami / 42056743969
93%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 209
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.176%. Remained the same
42056743969

push

github

web-flow 
docs: add changelog and require entries in PRs (#242)

* docs: add changelog with release history

Release notes exist only as GitHub Release bodies, which list PR titles
rather than what changed for users, and the repository has no record of
the changes waiting for the next release.

Add CHANGELOG.md in Keep a Changelog 1.0.0 format, with an Unreleased
section and an entry for each of the 62 tags, newest first. That
includes v0.0.1-beta.1 through beta.8, which have tags but no GitHub
Release. Entries are curated from release notes, commits, and PR
descriptions, and describe the effect on users. Breaking changes are
marked with **BREAKING:**, as in boot-service.

Dates use the UTC publish date of the GitHub Release, or the UTC tagger
date for the betas without one. This differs from the tag only for
v0.7.3, which was published the day after it was tagged. Each version
links to its comparison with the previous tag.

Where release notes disagree with the code at that tag, the entries
follow the code. For example, v0.8.0 added "smd group membership", not
"group membership".

Signed-off-by: Devon Bautista <17506592+synackd@users.noreply.github.com>

* docs: require changelog entries in PRs

CHANGELOG.md only stays useful if changes reach it as they merge, rather
than being reconstructed at release time.

Add a Changelog section under "Submitting Pull Requests" that says when
an entry is required, where it goes, and how to word it, with an
example, and add the step to "General PR Guidelines".

Require an entry for changes that users or Go API consumers would
notice. Exempt PRs with no user impact, such as tests, CI, refactors,
and routine dependency updates, so that Renovate PRs don't need editing
by hand. Security-relevant dependency updates still need an entry, which
a maintainer adds when a bot opened the PR.

Signed-off-by: Devon Bautista <17506592+synackd@users.noreply.github.com>

* docs: add changelog entry for v0.11.0

Move the Unreleased entries i... (continued)

13626 of 14624 relevant lines covered (93.18%)

762.16 hits per line

Jobs
ID Job ID Ran Files Coverage
1 42056743969.1 209
93.18
GitHub Action Run
Source Files on build 42056743969