Skip to content

Error when not using full SHA in set-commits #2064

Open

Description

When using set-commits as follows: sentry-cli releases set-commits "2.0" --commit "myRepo@be70b3b..25331bb", it looks like everything is working (no error or warning). However, because the provided commit SHAs aren't the full ones, it doesn't actually work. Hence, it would be great to output an error when the provided commit SHAs aren't the full ones.

Note: the docs mention that the full SHA is needed, but that's easy to miss.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions