. Kelvin is a Results-Driven and Goal-Oriented DevOps, Cloud and Linux Engineer.
He is equipped with extensive knowledge and excellent skills in DevOps and Cloud Engineering.
Kelvin is Open to work
What prefix would be best to use when you're making an update to a feature?
Let's assume you've already added the feature and you're now making an update to it, should you use chore or "update"?
👨🏫 Co-Founder of This is Learning, Organizer of AarhusJS
✍️ Writer, Speaker, FOSS Maintainer 📗 Author
🏆 Microsoft MVP 🌟 GitHub Star
🌊 Nx Champion 🦸 Angular Hero of Education
"refactor" changes the implementation of existing functionality. No observable change from the user's perspective.
"feat" can add a new feature or introduce breaking changes to existing functionality. Add "BREAKING CHANGES:" to the commit body or an exclamation point to the commit type, for example "feat!: make name parameter mandatory" for an API.
What prefix would be best to use when you're making an update to a feature?
Let's assume you've already added the feature and you're now making an update to it, should you use chore or "update"?
"refactor" changes the implementation of existing functionality. No observable change from the user's perspective.
"feat" can add a new feature or introduce breaking changes to existing functionality. Add "BREAKING CHANGES:" to the commit body or an exclamation point to the commit type, for example "feat!: make name parameter mandatory" for an API.
Does your update add a feature enhancement or simply change implementation. I would use feat for the former and change for the later.
You could also use feat, I wouldn’t want you to overthink it
I’m not really sure and I wouldn’t love to direct you wrongly