Commit FAQs

FAQs

💻 Q: If I need to add a new module only HTML and hardcoded, what type of commit should I set?

A: If you’re adding a new module that includes only HTML and is hardcoded, this still counts as a new feature. Use the feat type for the commit message. ✅

🔄 Q: If I only make a component dynamic, is it a feat?

A: Yes, making a component dynamic involves adding new functionality, so it should be categorized as a new feature. Use the feat type for the commit message. 🚀

📚 Q: Should I use fix for updating documentation with corrections?

A: No, corrections to documentation should use the docs type. The fix type is reserved for bug fixes in the codebase. 🐛

⚠️ Q: What should I do if my commit includes both a new feature and a bug fix?

A: It’s recommended to split the changes into separate commits, each with its appropriate type. This helps maintain a clear and concise commit history. 📝

NOTE!

Always ensure your commit messages are clear and descriptive. Use the appropriate type for each change and avoid combining different types in one commit. Even someone unfamiliar with coding should be able to understand your commit messages, so always think from that perspective!