Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[v1.60.0]
--bitbucket-username,--bitbucket-token, and--bitbucket-oauth-tokenflags in favour ofKF_BITBUCKET_*environment variables when authenticating to Bitbucket.kingfisher scansubcommands (for examplekingfisher scan github …) that translate into the legacy flags under the hood. The new layout keeps backwards compatibility while removing the wall of provider options fromkingfisher scan --help.--github-user,--gitlab-group,--bitbucket-workspace,--s3-bucket) still work but now emit a deprecation warning to encourage migration to the newkingfisher scan <provider>flow.kingfisher scan /path/to/dirflow for local filesystem / local git repo scans while adding a--list-onlyswitch to each provider subcommand so repository enumeration no longer requires the standalonegithub repos,gitlab repos, etc. commands.kingfisher github,kingfisher gitlab,kingfisher gitea,kingfisher bitbucket,kingfisher azure,kingfisher huggingface) now that enumeration lives underkingfisher scan <provider> --list-only.