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
This was brought to my attention thanks to #514 <_< thankfully GitHub automatically revokes leaked tokens.
When running git cliff -c github --github-repo orhun/git-cliff --verbose --debug the token is logged twice, once at the end for the RemoteConfig but also near the start for the Opt object. The second one does get sanitized but the fist one does not.
To reproduce
Steps to reproduce the behavior:
Set GITHUB_TOKEN env var
Run with -c github --github-repo orhun/git-cliff --verbose --debug arguments
See the token in the logs
Expected behavior
The token is sanitized in both places so it's safe to be copy-pasted and send for issue reports.
Describe the issue
This was brought to my attention thanks to #514 <_< thankfully GitHub automatically revokes leaked tokens.
When running
git cliff -c github --github-repo orhun/git-cliff --verbose --debug
the token is logged twice, once at the end for the RemoteConfig but also near the start for the Opt object. The second one does get sanitized but the fist one does not.To reproduce
Steps to reproduce the behavior:
-c github --github-repo orhun/git-cliff --verbose --debug
argumentsExpected behavior
The token is sanitized in both places so it's safe to be copy-pasted and send for issue reports.
Screenshots / Logs
Software information
Additional context
The text was updated successfully, but these errors were encountered: