Skip to content

LCORE-1457 Add SUPPORT.md, which appears with info when opening a GH issue #1315

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
max-svistunov wants to merge 1 commit into
base: main
Choose a base branch
from
Open

LCORE-1457 Add SUPPORT.md, which appears with info when opening a GH issue #1315

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/bug_report.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ assignees: ''

# Bug Description

## **Output of `OLS` version**
## **Lightspeed Stack version**

## **Describe the bug**

Expand Down
6 changes: 6 additions & 0 deletions SUPPORT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# Reporting bugs

* **External contributors**: Open a [GitHub Issue](https://github.com/lightspeed-core/lightspeed-stack/issues/new?template=bug_report.md) using the bug report template. For urgent issues, tag <!-- FIXME: is it fine @ptisnovs to tag you like this? --> in the issue.
Copy link
Contributor

@coderabbitai coderabbitai bot Mar 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Resolve the FIXME comment and complete the urgent issue guidance.

Line 3 contains an unresolved FIXME comment asking for confirmation about tagging someone, and the urgent issue escalation path for external contributors is incomplete. The text reads "For urgent issues, tag in the issue" without specifying who or what to tag.

Please resolve the following before merging:

  1. Confirm with @ptisnovs (or the appropriate person/team) whether they should be tagged for urgent issues
  2. Complete the guidance by either:
    • Specifying the person/team to tag (e.g., "tag @ptisnovs in the issue"), or
    • Providing alternative escalation instructions if tagging is not appropriate

Would you like me to suggest alternative escalation patterns commonly used in open-source projects?

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@SUPPORT.md` at line 3, Confirm with `@ptisnovs` whether they should be tagged
for urgent issues and then replace the HTML FIXME comment in the "For urgent
issues..." line: either explicitly instruct "For urgent issues, tag `@ptisnovs` in
the issue" if they agree, or update the guidance to an alternative escalation
path (e.g., "For urgent issues, open an issue, add the 'urgent' label, and
notify the maintainers via the org Slack `#support` or mention the `@maintainers`
team") so the FIXME is removed and the urgent-escalation step is fully
specified.

* **Red Hat contributors**: File a bug in [Jira](https://issues.redhat.com) under the Lightspeed Core (LCORE) project. For urgent issues, ping `@ls-core-team` on Slack in the `#forum-lightspeed` channel.

In both cases, include: steps to reproduce, expected vs. actual behavior, and the Lightspeed Stack version.
Loading