mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-26 21:47:20 +00:00
pulse-triage[bot]
6409a38480
Existing forms warn against uploading secrets but stop at prevention. Explain issuer revocation, separate attachment removal, surviving copies, private follow-up and independent monitoring coverage without asking for another diagnostic or credential test. Change-source: pulse-maintainer Contract-Neutral: Documentation and guidance coverage only; runtime, API, storage and deployment contracts are unchanged.
70 lines
2.9 KiB
YAML
70 lines
2.9 KiB
YAML
name: Feature request
|
|
description: Describe one operator problem or workflow Pulse could improve
|
|
title: "[Feature]: "
|
|
labels:
|
|
- enhancement
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Lead with one primary operator outcome. If context exposes another actionable topic, list it in the dedicated field below; triage will preserve it rather than silently folding it into the primary request.
|
|
|
|
Anything you attach here is public. Review files and screenshots locally before posting, even when an export is labelled "sanitized". Remove credentials, session cookies, secret URLs, private host/network and personal details, including text echoed in errors. Do not attach full/private diagnostics, .env or configuration files, private keys, Copy as cURL commands or full network exports.
|
|
|
|
If a credential has already been posted, revoke it with its issuer and remove the public copy; editing a post is not revocation or proof that every copy is gone. Do not repost the original evidence; use the [private security disclosure route](https://github.com/rcourtman/Pulse/security/policy) for sensitive details.
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: Problem
|
|
description: What are you trying to accomplish, and what makes it difficult today?
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: current_workflow
|
|
attributes:
|
|
label: Current workflow
|
|
description: Describe how you handle this now. Include the relevant platform, Pulse page, deployment type, and constraints.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: desired_outcome
|
|
attributes:
|
|
label: Desired outcome
|
|
description: What would a successful Pulse workflow let you do? Focus on the outcome rather than prescribing an implementation when possible.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives considered
|
|
description: What workarounds, other tools, or different approaches have you tried?
|
|
|
|
- type: textarea
|
|
id: additional_topics
|
|
attributes:
|
|
label: Additional actionable topics
|
|
description: Enter "None" for a single request. If the context also raises another bug, feature, or workflow, list each topic here; triage will preserve it with a separate linked disposition.
|
|
placeholder: None
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: additional_context
|
|
attributes:
|
|
label: Additional context
|
|
description: |
|
|
Add screenshots, examples, or related issues if useful.
|
|
Review files and screenshots locally; remove secrets and identifying details, including those echoed in errors, before attaching them here.
|
|
|
|
- type: checkboxes
|
|
id: confirmations
|
|
attributes:
|
|
label: Confirmations
|
|
options:
|
|
- label: I searched existing issues for duplicates.
|
|
required: true
|