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
At the moment, actions-riff-raff automatically produces one PR commentper riff-raff artifact - this gets noisy on projects with many artifacts - eg Ophan, with 8 comments, or editorial-tools-platform, with 12 comments.
We don't want developers to have to hunt for non-bot comments on PRs - the human-written comments on PRs are generally the most important ones, and shouldn't be lost in a swarm of bot comments! Consequently, we should restrict the automatic commenting by actions-riff-raff to one comment per PR - with that comment updated as new artifacts (and ideally commits) arrive.
I think producing one comment is likely the best behaviour, however it's worth mentioning an alternative that exists today would be to split across GitHub workflow files. The guardian/deploy-tools-platform repository does this, for example. The trade-off is increased complexity to the workflow files, with the setting of paths within the on directive.
At the moment,
actions-riff-raff
automatically produces one PR comment per riff-raff artifact - this gets noisy on projects with many artifacts - eg Ophan, with 8 comments, or editorial-tools-platform, with 12 comments.We don't want developers to have to hunt for non-bot comments on PRs - the human-written comments on PRs are generally the most important ones, and shouldn't be lost in a swarm of bot comments! Consequently, we should restrict the automatic commenting by
actions-riff-raff
to one comment per PR - with that comment updated as new artifacts (and ideally commits) arrive.See also some previous comments about this issue:
The text was updated successfully, but these errors were encountered: