From da2e29969663161cfad08792f82f8b73d58f12df Mon Sep 17 00:00:00 2001 From: Andrey Petrov Date: Tue, 16 Aug 2016 14:42:38 -0400 Subject: [PATCH] on commit messages --- FAQ.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/FAQ.md b/FAQ.md index bfd8b9f..b182ce7 100644 --- a/FAQ.md +++ b/FAQ.md @@ -57,11 +57,11 @@ Now you can make your changes. Once you've finished that, you will then have to staged for committing. Once added, we can create a commit message, and push it to your fork repository. ``` bash -$ git add newfile.txt # Add any new files -$ git commit -m "Fixed not having a file.txt in the project" +$ git add host_test.go # Add any new files +$ git commit -m "sshchat: Added host tests." ``` -Try to keep commit messages [similar to the style the project already uses](https://github.com/shazow/ssh-chat/commits/master). +Try to keep commit messages [similar to the style the project already uses](https://github.com/shazow/ssh-chat/commits/master). Generally we prefix commit titles with the package name or topic of the change to make it easy to convert commit messages into change logs. Now the changes are ready to be pushed. Currently, Git doesn't know where to push these changes, since we're on a different branch. We need to set a remote that we can push these changes to.