-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the ability to add prefix to comment output #1716
Comments
Regarding this and #1715 I heard a feature request to introduce some sort of templating override for powerusers who want to structure their comments in different ways. Perhaps a "digger.mustache.tpl" file that lives somewhere and instrucructs digger what to include in the outputs somehow. Unformed thoughts, but it seems that its inevetible to allow for powerusers of comments to customise them heavily |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Currently, Digger supports $DIGGER_OUT in workflow custom steps to display output back into the PR comment. This is put into a section block Additional Outputs which is hidden by default.
I would like there to be a way to target a different output variable to prepend before any other comment output. We have done this with security scanning using a custom variable called $DIGGER_PREFIX_OUT. Here is an example image of the output comment using $DIGGER_PREFIX_OUT instead of $DIGGER_OUT:
This would provide more power to customizing the information in the PR to the user for custom extension on top of Digger (security, format, cost, etc)
The text was updated successfully, but these errors were encountered: