Skip to content
This repository was archived by the owner on Sep 9, 2020. It is now read-only.

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

Merged
merged 1 commit into from
Jul 2, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/new-project.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down