Skip to content

Add config and persona hint for Gemini Code Assist#4555

Open
psss wants to merge 2 commits intomainfrom
psss-gemini-config
Open

Add config and persona hint for Gemini Code Assist#4555
psss wants to merge 2 commits intomainfrom
psss-gemini-config

Conversation

@psss
Copy link
Contributor

@psss psss commented Feb 5, 2026

Let's try if we can tune up Gemini's behaviour to our needs.
https://developers.google.com/gemini-code-assist/docs/customize-gemini-behavior-github

Let's try if we can tune up Gemini's behaviour to our needs.
@gemini-code-assist
Copy link
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@psss psss added this to planning Feb 5, 2026
@github-project-automation github-project-automation bot moved this to backlog in planning Feb 5, 2026
@psss psss added the area | process The way how we collaborate on the development label Feb 5, 2026
max_review_comments: -1
pull_request_opened:
help: false
summary: true
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this the "Summary of Changes" thing that is posted the first time a PR is opened? Shall we disable it, since it seems it only regurgitates the content of the description, and best guesses of the changes. If anything we should be making sure that the contents of the description is up to date and describes the PR well enough rather than the comment it generates there.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Makes sense, let's turn it off: 08b4710

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmmm... thinking about it a bit more... actually, gemini is quite good at providing summaries and sometimes it describes the changes better than our commit descriptions. It can also serve as an inspiration for improving the pull request description. Now I'm not completely sure we should disable it...

Copy link
Contributor

Choose a reason for hiding this comment

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

Afaict (example), it does not update the summary with each commit made, and if that is the case it would be a source of distraction when it comes to reviewing what is the overall PR state.

@psss psss requested a review from LecrisUT February 10, 2026 21:44
@LecrisUT
Copy link
Contributor

Anpther issue spotted. This one is so repetitive: #4571 (comment). It is the same change repated, we know to update all ocurances

@psss psss added this to the 1.68 milestone Feb 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area | process The way how we collaborate on the development

Projects

Status: backlog

Development

Successfully merging this pull request may close these issues.

3 participants