Adding more emphasis to the need of create a go file before running ensure

This commit is contained in:
Felipe Rodrigues 2018-06-26 23:24:25 -03:00 коммит произвёл GitHub
Родитель 1550da37d8
Коммит d7c2809137
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 1 добавлений и 1 удалений

Просмотреть файл

@ -28,7 +28,7 @@ In a new project like this one, both files and the `vendor` directory will be ef
This would also be a good time to set up a version control, such as [git](https://git-scm.com/). While dep in no way requires version control for your project, it can make inspecting the changes made by normal dep operations easier. Plus, it's basically best practice #1 of modern software development!
At this point, our project is initialized, and we're ready to start writing code. You can open up a `.go` file in an editor and start hacking away. Or, after creating your first `.go` file, you can go ahead and pre-populate your `vendor` directory with some projects that you already know that you'll need:
At this point, our project is initialized, and we're ready to start writing code. You can open up a `.go` file in an editor and start hacking away. Or, **after creating your first `.go` file**, you can go ahead and pre-populate your `vendor` directory with some projects that you already know that you'll need:
```bash
$ dep ensure -add github.com/foo/bar github.com/baz/quux