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
Describe the bug:
The vast majority of recent commits generated by @wet-boew-bot in this repo are empty. As in, they're just "hollow" commit messages with 0 changed files.
That might not necessarily be a bug in and of itself, but it adds lots of unnecessary bloat to the repo's commit history. Not to mention that it makes it practically impossible to find anything meaningful in GitHub's commit history section (it doesn't distinguish commits associated to changed files).
@duboisp@delisma Could the bot be updated to only generate commits when files have been changed?
Describe the bug:
The vast majority of recent commits generated by @wet-boew-bot in this repo are empty. As in, they're just "hollow" commit messages with 0 changed files.
That might not necessarily be a bug in and of itself, but it adds lots of unnecessary bloat to the repo's commit history. Not to mention that it makes it practically impossible to find anything meaningful in GitHub's commit history section (it doesn't distinguish commits associated to changed files).
@duboisp @delisma Could the bot be updated to only generate commits when files have been changed?
Thanks :)!
To Reproduce:
Expected behaviour:
All commits should contain changed files.
Actual behaviour:
Many recent commits contain 0 changed files.
The text was updated successfully, but these errors were encountered: