github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Can you provide a code review feature based on ChatGPT? #10402

New Issue
Closed
opened 2025-11-02 09:06:35 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 09:06:35 -06:00
Owner
Copy Link

Originally created by @vicnoah on GitHub (Mar 9, 2023).

Feature Description

The Curve storage team is experimenting with this feature recently, and I think it could be very useful.

Screenshots

mmexport1678329871219

Originally created by @vicnoah on GitHub (Mar 9, 2023). ### Feature Description The Curve storage team is experimenting with this feature recently, and I think it could be very useful. ### Screenshots ![mmexport1678329871219](https://user-images.githubusercontent.com/20820831/223902805-59f2a8f9-c4fb-482f-8fb6-fa7c98c921b9.jpg)
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 09:06:35 -06:00
GiteaMirror commented 2025-11-02 09:06:36 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Mar 9, 2023):

This seems like something for a CI to do, and would let people use whichever LLM is the hot thing at that time.

@jolheiser commented on GitHub (Mar 9, 2023): This seems like something for a CI to do, and would let people use whichever LLM is the hot thing at that time.
GiteaMirror commented 2025-11-02 09:06:36 -06:00
Author
Owner
Copy Link

@vicnoah commented on GitHub (Mar 9, 2023):

This seems like something for a CI to do, and would let people use whichever LLM is the hot thing at that time.

This functionality does seem more appropriate for CI to handle. However, the results from ChatGPT can only be used as a reference, since it sometimes provides incorrect results. Using CI might not be the best option either. My suggestion is to provide some reference suggestions based on ChatGPT's analysis of the code as an auxiliary tool during code review, in the code merging window.

@vicnoah commented on GitHub (Mar 9, 2023): > This seems like something for a CI to do, and would let people use whichever LLM is the hot thing at that time. This functionality does seem more appropriate for CI to handle. However, the results from ChatGPT can only be used as a reference, since it sometimes provides incorrect results. Using CI might not be the best option either. My suggestion is to provide some reference suggestions based on ChatGPT's analysis of the code as an auxiliary tool during code review, in the code merging window.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/feature type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10402
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?