Let GitHub Copilot write commits your way 🚀 Most developers don’t know this trick 👀 You can teach GitHub Copilot how to generate commit messages exactly the way you want — Conventional Commits, emojis, or even Spanish formats This works both in VS Code and Visual Studio 🧑💻 With one simple configuration line, you can: ✅ Standardize your commit history ✅ Keep your changelogs clean ✅ Save time while staying consistent 💡 In my case, I tell Copilot to follow the Conventional Commits format You can see the full setup step-by-step in the carousel. I’ll leave the JSON snippet in the comments, or you can grab it from this GitHub Gist 👇 👉 https://lnkd.in/eynpFxcW Always review the generated commit message before committing — make sure it actually reflects what changed and why. Copilot helps a lot, but you’re still the brain behind your code 🔁 Save this post for later 💬 Comment if you’d like my version in English / Spanish / Emoji style ❤️ or share it with your team to keep your commits clean and consistent #githubcopilot #visualstudio #vscode #conventionalcommits #productivity #developertools #commitmessages
Bayron Rodezno
6mo
Great info! Thanks crack!
Code snippet "github.copilot.chat.commitMessageGeneration.instructions": [ { "text": "Use the Conventional Commits format. Valid types: feat, fix, test, docs, refactor, chore, style, perf. Example: feat(invoice): add amount validation. The first line should not exceed 72 characters. The second line should be blank. Starting with the third line, write a more detailed description in explaining the reason for the change and any additional context. Use bullet points if there are several important points." } ]