leap-16.1 Update from Factory #3
Reference in New Issue
Block a user
Delete Branch "michals/gitea-tea:leap-16.1"
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?
- feat: add validation for object-format flag in repo create command (see gh#openSUSE/openSUSE-git#60) - Fix release version - update gitea sdk to v0.22 - don't fallback login directly - Check duplicated login name in interact mode when creating new login - Fix bug when output json with special chars - add debug mode and update readme - update go.mod to retract the wrong tag v1.3.3 - revert completion scripts removal - Remove pagination from context - Continue auth when failed to open browser - Fix bug - Fix tea login add with ssh public key bug - Add temporary authentication via environment variables - Fix attachment size - deploy image when tagging - Add Zip URL for release list - Use bubbletea instead of survey for interacting with TUI - capitalize a few items - rm out of date comparison file - README: Document logging in to gitea - remove autocomplete command - chore(deps): update ghcr.io/devcontainers/features/git-lfs docker tag to v1.2.5 - replace arch package url - fix: Reenable `-p` and `--limit` switches - Remove upstreamed patch: OBS-URL: https://build.opensuse.org/package/show/devel:tools:scm/gitea-tea?expand=0&rev=18Review by packagehub-review represents a group of reviewers: bigironman, lkocman-factory, maxlin_factory, smithfarm .
Do not use standard review interface to review on behalf of the group.
To accept the review on behalf of the group, create the following comment:
@packagehub-review: approve.To request changes on behalf of the group, create the following comment:
@packagehub-review: declinefollowed with lines justifying the decision.Future edits of the comments are ignored, a new comment is required to change the review state.
Obsoletes #2
Legal reviewed as acceptable:
Unfortunately #2 was merged since it's not closed, so now the file confliciting caused this PR being unmergeable. Could you please rebase your branch?
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.