New resource reader capabilities
What does this MR do and why?
This MR retires using SummarizeComments tool from usage in chat. Instead, I have added comments to the serialized issue. This way, LLM has access to all data around issue (title, description, comments etc), so can answer more comprehensive questions.
I also have added one question to questions.yml file to capture difference between summarizing issue - LLM is taking into consideration all the data about issue - and summarizing comments.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
- Use zero shot rake task to see answers to the issue-related questions.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
assigned to @mksionek
- A deleted user
added backend label
8 Warnings ce78b83d: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines. 2a468ef5: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. 515734b9: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. f41b3303: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines. f158bf27: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines. 1829b7c1: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines. Please add a merge request subtype to this merge request. Please add a merge request type to this merge request. 1 Message CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, add the
Changelog
trailer to the commit message you want to add to the changelog.If you want to create a changelog entry for GitLab EE, also add the
EE: true
trailer to your commit message.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer backend Dzmitry Meshcharakou (
@dmeshcharakou
) (UTC+2, same timezone as@mksionek
)Charlie Ablett (
@cablett
) (UTC+12, 10 hours ahead of@mksionek
)To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerEdited by Ghost UserAllure report
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for ce78b83dexpand test summary
+-----------------------------------------------------------------------+ | suites summary | +------------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +------------------+--------+--------+---------+-------+-------+--------+ | Verify | 8 | 0 | 0 | 5 | 8 | ❗ | | Manage | 13 | 0 | 1 | 12 | 14 | ❗ | | Govern | 21 | 0 | 0 | 12 | 21 | ❗ | | Plan | 51 | 0 | 0 | 12 | 51 | ❗ | | Package | 0 | 0 | 1 | 0 | 1 | ➖ | | Data Stores | 22 | 0 | 0 | 10 | 22 | ❗ | | Framework sanity | 0 | 0 | 1 | 0 | 1 | ➖ | | Create | 27 | 0 | 1 | 20 | 28 | ❗ | | Monitor | 4 | 0 | 0 | 0 | 4 | ✅ | +------------------+--------+--------+---------+-------+-------+--------+ | Total | 146 | 0 | 4 | 71 | 150 | ❗ | +------------------+--------+--------+---------+-------+-------+--------+
Edited by Ghost User @mksionek, please can you answer the question: Should this have a feature flag? to help with code review for the Authentication and Authorization group.This nudge was added by this triage-ops policy.
added groupai framework label and removed groupauthentication and authorization [DEPRECATED] label
- Resolved by Alexandru Croitor
@mksionek - please see the following guidance and update this merge request.1 Error Please add typebug typefeature, or typemaintenance label to this merge request.
Setting label(s) ~"Category:GitLab Duo Chat" devopsmodelops sectiondata-science based on groupai framework.
added devopsmodelops sectiondata-science labels
Setting label(s) ~"Category:GitLab Duo Chat" based on groupai framework.
added 2 commits
added 1 commit
- 9deed083 - Add one question to prove the reliability of the changes