Skip to content

tests: PR for testing CI changes #361

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

Closed
Artemon-line wants to merge 9 commits into from
Closed

tests: PR for testing CI changes #361

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
66890fe
docs: add testing section to README
Artemon-line May 12, 2026
17f84d4
test: trigger CI with no-op change to tests/
Artemon-line May 12, 2026
7d56657
Merge branch 'main' into test-vertext-run
Artemon-line Jun 9, 2026
3749850
Merge branch 'main' into test-vertext-run
Artemon-line Jun 9, 2026
0c11617
Merge branch 'main' into test-vertext-run
Artemon-line Jun 12, 2026
581b409
Merge branch 'main' into test-vertext-run
Artemon-line Jun 19, 2026
b887946
Merge branch 'main' into test-vertext-run
Artemon-line Jun 29, 2026
e131773
refactor: remove pgvector extension enabling logic from setup-postgre…
Artemon-line Jun 30, 2026
6a3b62f
Merge branch 'main' into test-vertext-run
Artemon-line Jul 7, 2026
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: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
# TESTING

Comment on lines +1 to +2

@coderabbitai coderabbitai Bot May 12, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

TESTING section is empty and does not provide executable test guidance.

Add concrete test steps (commands, prerequisites, and expected pass/fail signals). As-is, contributors get no actionable testing procedure from this section.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 1 - 2, Update the README's TESTING section to include
concrete, executable test steps: list prerequisites (e.g., required Node/Python
version, environment variables, services to run), provide exact commands to run
unit, integration, and E2E tests (e.g., npm test, pytest, or ./run-tests.sh),
show expected success indicators (exit code 0, passing test counts, or specific
log lines) and failure signals (non-zero exit codes or failed test counts), and
include any teardown or common troubleshooting tips; ensure these instructions
are placed under the "TESTING" header so contributors can follow them
end-to-end.

# Open Data Hub Llama Stack Distribution

[![Build](https://github.com/opendatahub-io/llama-stack-distribution/actions/workflows/redhat-distro-container.yml/badge.svg?branch=main)](https://github.com/opendatahub-io/llama-stack-distribution/actions/workflows/redhat-distro-container.yml)
Expand Down
Loading