Skip to content
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.

Sign up for GitHub

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

Jump to bottom

gitea dump add quiet option #19687

Closed
chmouel opened this issue May 12, 2022 · 0 comments · Fixed by #22969
Closed

gitea dump add quiet option #19687

chmouel opened this issue May 12, 2022 · 0 comments · Fixed by #22969
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@chmouel
Copy link

chmouel commented May 12, 2022

Feature Description

It would be nice if we can have a quiet option to gitea dump, this would be useful for cron combined with -f-.

I can use 2>/dev/null but in case of error then I won't see it anymore,

Screenshots

image
@chmouel chmouel added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels May 12, 2022
fredrik-eriksson added a commit to fredrik-eriksson/gitea that referenced this issue Feb 18, 2023
@fredrik-eriksson
Add --quiet option to gitea dump
5a1f90d 
Fixes: go-gitea#19687
@fredrik-eriksson fredrik-eriksson mentioned this issue Feb 18, 2023
Merged
jolheiser pushed a commit that referenced this issue Apr 10, 2023
@fredrik-eriksson
Add --quiet option to gitea dump (#22969)
cb15364 
Fixes: #19687

The --quiet options to gitea dump silences informational and less
important messages, but will still log warnings and errors to console.
Very useful in combination with cron backups and '-f -'.

Since --verbose and --quiet are incompatible with each other I made it
an error to specify both. To get the error message to be printed to
stderr I had to make this test after the NewServices()-call, which is
why there are three new blocks of code instead of two.
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add --quiet option to gitea dump fredrik-eriksson/gitea
1 participant
@chmouel