Skip to content

Fix issue #1668: Provide a /packit help comment command #3069

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
JackDKobe wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix issue #1668: Provide a /packit help comment command #3069

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6482e73
Fix issue #412: enable controlling packit-service with the command
Mar 22, 2026
35a0f81
Fix issue #1668: Provide a /packit help comment command
Mar 22, 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
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,3 +15,9 @@ If you'd like to know more about packit, please check:
- Our website: [packit.dev](https://packit.dev/)
- GitHub project for packit tool: [packit-service/packit](https://github.com/packit/packit)
- Hacking on packit service: [CONTRIBUTING.md](/CONTRIBUTING.md)


<!-- fix-issue-412: enable controlling packit-service with the command embedded -->


<!-- fix-issue-1668: Provide a /packit help comment command -->
Comment on lines +18 to +23
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot Mar 22, 2026

Choose a reason for hiding this comment

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

medium

These additions introduce several empty lines which makes the file less clean. Please consider removing them.

Also, the comment for issue #412 seems unrelated to this pull request. It might be better to handle that in a separate PR to keep changes focused.

Loading