Maintain conversation/dialogue context when answering to GitHub comments

[Nayjest]

• Pull valuable previous comments
• Add it to LLM context

[harryd337]

Is the plan to add the context of comments in a PR to the Gito review? It would be really useful to be able to write a quick comment that it can read in all future reviews telling it to ignore certain issues we are deliberately addressing in a future PR

[Nayjest]

@harryd337 I've created a separate issue:

#230 Consider PR description and comments in PR reviews

It should address your feature request and generally should be useful to enrich CR context with this data.

(Right now Gito only considers the task descriptions from Jira / Linear during review (if configured), but not the PR description + comments.)

There are possible drawbacks in the form of significant growth in consumed tokens, as the review prompt is applied separately to each changed file
(depending on how much content you have in the PR description + comments).

How to configure Gito to ignore some issues in current implementation:
Edit the .gito/config.toml file in your repo and put additional instructions into the requirements variable in prompt_vars section.

Example:

(Or alternatively, you can override the whole review prompt template.)

[ Another Idea ]

I think what you would typically ask for in comments will likely be relevant to your entire codebase.

So maybe it's worth adding some kind of conversational function like reacting to comment "@gito, add the following rule: ignore code indent issues" — which would extract your rule using an LLM from the comment and put it into .gito/config.toml with a distinct commit.

[ Tips ]
(Right now there are 3 functions supported for reacting to review comments:

• Fixing issues / applying proposals generated in the latest CR report: put comment like @gito fix 1, 2, 3
• Answering questions about the associated changeset: @gito ....your question here...
• Triggering code reviews from workflow dispatch: @gito review

You need to have .github/gito-react-to-comments.yml workflow to activate this functionality.
)

[harryd337]

@Nayjest thanks for the detailed response and helpful tips. Yes I think I will make use of customising the requirements variable for now until that feature is developed.