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
Just like the comment on alert feature, it would be nice if the action could open a new issue on alert and/or with the results. This way, the action does not have to be linked to a PR, for example if we want to have a scheduled benchmarking run on a certain branch.
This would go hand in hand with #154 (Output a Markdown result directly for custom integration), as there could be one common representation of the result that could be used in the comment, job summary, new issue, or direct for custom integration.
The text was updated successfully, but these errors were encountered:
Thank you for creating this issue. Implementing #154 would allow us to easily integrate the creation of an issue on alert as a separate step. That could be the first step to enable this functionality.
What would be the use case for this option though? How would you imagine this creation of an issue work? Just add a configuration option similar to comment-on-alert and let the user of the action figure out when to enable it?
Thanks for your answer. The use case is keeping track of the performance on every new merge into the main branch, and have the result displayed in a new issue (in case of alert). This way, the action doesn't have to be linked to a PR. And yes, I imagine the creation of the issue to be similar as comment-on-alert.
Just like the comment on alert feature, it would be nice if the action could open a new issue on alert and/or with the results. This way, the action does not have to be linked to a PR, for example if we want to have a scheduled benchmarking run on a certain branch.
This would go hand in hand with #154 (Output a Markdown result directly for custom integration), as there could be one common representation of the result that could be used in the comment, job summary, new issue, or direct for custom integration.
The text was updated successfully, but these errors were encountered: