add issues export/import
#132
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#132
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?
a function witch can create issues from a csv or yaml file witch was created by tea via
tea issues -o yaml
so you can backup and restore issues easely
acc `issues import` -b ato add `issues import`We can't cover this use case fully at the moment, as the API (afaik) does not provide a way to set the author of an issue.
Also
tea issues ls
does not output the issue body, we might need a field-selection mechanism like intea repos ls
for thatadd `issues import`to add `issues export/import`@noerw agree, I think we at first infent a
export
, so tea can be used as backup tool for repos hosted on a gitea instance you are not admin at (gitea.com for example).and for a import you have to be admin on an instance ... then you can use the sudo header to pretend to be user XY ... so I would add two functions: one with sudo and wone who write into body who original was the author ...