-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
Related issues buildout #9
Conversation
This commit introduces issue linking functionality. A new table and associated model `issue_links` have been added to allow issues to have various types of links to other issues. It also includes indexes for quicker searching and linking. In addition, a `parent_id` field was added to the issues table and model, allowing issues to have a parent-child relationship. The concept of linked issues and parent/child issues can help to model complex relationships between tasks.
The code now allows Issues to be linked with each other and also fetches linked issues as part of the issue information. Changes have been made on the back-end database models to accommodate this functionality, while the GraphQL implementation has been updated to carry the linked issue details alongside the main issue information.
Two new parameters, search and searchOperator, are now added to the QueryIssueInput in type definitions. This will allow filtering issues based on specific search terms and operators.
Added a new property, `inverseLinkType`, to outline the possible inverse link types between issues in `issue-links.js`. This change also required updates to `issue.js` to handle both linked issues and linked by issues. Additionally, the related resolvers have been adjusted to accommodate these changes. This improvement enables a more comprehensive display of issue relationships within the system.
The code for handling the absence of an authorization header has been changed. The previous implementation used an empty string as a default value for the token if it was not found in the request headers. Now, the 'token' variable will be set to 'undefined' if the 'authorization' header is not present.
PR Analysis
PR Feedback
How to useInstructions
|
@CodiumAI-Agent /describe |
A new GitHub Actions workflow has been added. This workflow, defined in pr_agent.yml, is triggered on pull requests and issue comments. It runs a job, pr_agent_job, that uses the PR agent from Codium-ai/pr-agent. It allows the job to write to issues, pull requests, and contents.
A name has been added to the `.github/workflows/pr_agent.yml` file to improve clarity. This will help in identifying and managing the workflow associated with pull requests and issue comment activities.
This commit updates the settings in the PR agent workflow file. Specifically, it disables the need for tests review by the PR reviewer and limits the number of code suggestions to 1.
The value indicating how many code suggestions the pull request agent should provide was removed. This change makes the PR agent more flexible by not restricting the number of code suggestions it can offer.
/describe |
No description provided.