• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

cameri / nostream / 43900988690
79%

Build:
DEFAULT BRANCH: main
Ran 16 Nov 2026 03:54PM UTC
Jobs 2
Files 339
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

16 Nov 2026 03:51PM UTC coverage: 78.146%. Remained the same
43900988690

push

github

web-flow
chore: modernize the issue templates as GitHub forms (#1146)



## Description
Replaces the two legacy markdown issue templates with the set proposed
in #857.

- `config.yml`: turns blank issues off so every issue starts from a
template, and adds contact links for private vulnerability reporting
(GitHub Security Advisories), the development chat, the Nostr protocol
chat and the website, the three links the issue lists.
- `bug_report.yml`: a form with the fields a maintainer needs to
reproduce a bug (what happened, relay version, deployment, OS, NIPs
involved, logs, reproduction steps, extra context).
- `feature_request.yml`: a form (problem, proposed solution,
alternatives, pledge amount, extra context) that keeps the pledge
paragraph of the old template word for word.
- `documentation.yml`: a form for gaps in the docs, README or website.
- `security_report.md`: a markdown template, since a form cannot be
private, that tells the reporter not to describe a vulnerability in a
public issue and to use private vulnerability reporting.
- Removed `bug_report.md` and `feature_request.md`.

The forms set no title prefix and no default assignee. The old templates
assigned `Cameri` to every issue and started the title with `[BUG] ` /
`[REQUEST]`, which had to be deleted by hand each time.

A unit test (`test/unit/ci/issue-templates.spec.ts`) checks the set:
blank issues are off, the security link points to private reporting,
every form has a name, a description, labels the repository has, unique
field ids, valid element types and a required field, the pledge
paragraph is intact, and the legacy templates are gone.

## Related Issue
Closes #857

## Motivation and Context
Without a `config.yml` GitHub shows raw markdown links instead of the
template chooser and allows blank issues, and the legacy templates were
generic. Structured fields mean a report arrives with the version,
deployment and logs a maintainer would otherwise have to ask for.

## How Has This Been T... (continued)

5302 of 7396 branches covered (71.69%)

Branch coverage included in aggregate %.

11279 of 13822 relevant lines covered (81.6%)

676.17 hits per line

Jobs
ID Job ID Ran Files Coverage
1 Integration - 43900988690.1 16 Nov 2026 03:54PM UTC 339
33.46
GitHub Action Run
2 Unit - 43900988690.2 16 Nov 2026 03:57PM UTC 339
76.03
GitHub Action Run
Source Files on build 43900988690
  • Tree
  • List 339
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #43900988690
  • 5b1040bc on github
  • Prev Build on main (#43899400692)
  • Next Build on main (#43917979809)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc