You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running in GitHub actions when triggering the job from the tag itself, chalk will misreport the tag as not being signed/annotated. This is upstream issue in checkout action:
Should chalk attempt to automatically git fetch the appropriate tag if git command is present?
As we report signing information I can see how that can be used for compliance however wrong information is not very helpful. I think we should attempt to remedy that officially with chalk to ensure tag information is up to date.
The text was updated successfully, but these errors were encountered:
When running in GitHub actions when triggering the job from the tag itself, chalk will misreport the tag as not being signed/annotated. This is upstream issue in checkout action:
actions/checkout#290
actions/checkout#882
actions/checkout#697
actions/checkout#1506
Should chalk attempt to automatically
git fetch
the appropriate tag ifgit
command is present?As we report signing information I can see how that can be used for compliance however wrong information is not very helpful. I think we should attempt to remedy that officially with chalk to ensure tag information is up to date.
The text was updated successfully, but these errors were encountered: