tea comands for reviews #131
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#131
Loading…
Reference in New Issue
Block a user
No description provided.
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?
...
idears:
tea pr lgtm
https://github.com/go-gitea/gitea/pull/11224 bring api for reviews - use them
I'll try it
@crapStone https://gitea.com/gitea/go-sdk/src/branch/master/gitea/pull_review.go has the func you need :)
so you basically want to approve a pr?
what do you think of:
tea pr lgtm
as approve shortcut andtea pr review deny/accept/comment/reject(upcoming...) -text-
@6543 Whats the difference between deny and reject?
I propose
An epic feature idea: Maybe we can pipe in a patch-mail and parse that into code comments? ?
So an input like
would translate to
if called via
If there is a golang git patch parser, this could actually be doable
edit: https://github.com/sourcegraph/go-diff might work
missingtea pr comment <idx> <comment>
but I think this is it 👍right I think review is the way to go, since comment indicate you append a comment onto this pull - a subcomand we should add if we show comments of issues/pulls ...
I like reject.