Skip to content

Conversation

@blkt
Copy link
Contributor

@blkt blkt commented Nov 15, 2024

The command frizbee actions <action>@<tag> incorrectly retrieves the tag's ref rather than the commit's one. The tag's ref should instead be used to retrieve the details of the tag, which contain the ref of the commit.

This change changes getCheckSumForTag to lookup the right field using two subsequent call to GitHub.

Fixes #206

@blkt blkt self-assigned this Nov 15, 2024
@blkt blkt requested review from JAORMX, jhrozek and rdimitrov November 15, 2024 20:20
@blkt blkt force-pushed the fix/frizbee-action-invalid-commit-ref branch from 1e136a0 to 22b52e1 Compare November 15, 2024 21:34
@coveralls
Copy link

coveralls commented Nov 15, 2024

Coverage Status

coverage: 52.926% (+0.09%) from 52.832%
when pulling aae8b7a on fix/frizbee-action-invalid-commit-ref
into c2a623a on main.

@blkt blkt force-pushed the fix/frizbee-action-invalid-commit-ref branch from 22b52e1 to c5a341c Compare November 15, 2024 21:37
The command `frizbee actions <action>@<tag>` incorrectly retrieves the
tag's ref rather than the commit's one. The tag's ref should instead
be used to retrieve the details of the tag, which contain the ref of
the commit.

This change changes `getCheckSumForTag` to lookup the right field
using two subsequent call to GitHub.

Fixes #206
@blkt blkt force-pushed the fix/frizbee-action-invalid-commit-ref branch from c5a341c to aae8b7a Compare November 15, 2024 21:52
@blkt blkt changed the title Retrieve commit ref correctly. Resolve commit ref correctly. Nov 15, 2024
@blkt blkt merged commit fbef552 into main Nov 18, 2024
8 checks passed
@blkt blkt deleted the fix/frizbee-action-invalid-commit-ref branch November 18, 2024 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

frizbee actions generates wrong/invalid commit ref?

4 participants