27
Is there a way to hide dependabot commits in the history of a repo?
(lemmy.pe1uca.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Oct 2024
27 points (100.0% liked)
Programming
17303 readers
41 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
BTW I hope any project won’t increase the Z version only by including Dependabot commits, it would be insane. Release must be documented, tested, with CHANGELOG updated. If some maintainers just accept Dependabot commits without checking, move away. That’s just simple crappy auto-merge.
Must include CHANGELOG...
The changelog:
It's not a must [unless you put it into a contract], it's a should or would be nice
Many, if not most, projects don't follow a good, obvious, transparent, documented release or change management.
I wish for it, too, but it's not the reality of projects. Most people don't seem to care about it as much as I do.
I agree blind acceptance/merging is problematic. But for some projects (small scope/size/personal-FOSS, trustworthy upstream) I see it as pragmatic rather than problematic.