Skip to content
Go Programming Language Course
Go
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add samuong to CODEOWNERS Jul 18, 2019
00_hello_world/juliaogris Remove testify from hello world test May 15, 2019
01_fib Add lab 1, Fibonacci numbers (#622) Oct 6, 2019
02_bubble Add lab 2, bubblesort (#624) Oct 30, 2019
03_letters Add lab 3 - Letter Frequency (#638) Oct 18, 2019
04_numeronym Add lab 4 - Numeronym (#640) Nov 9, 2019
05_stringer
06_puppy Add lab 6 - CRUD Puppy with interface (#653) Nov 5, 2019
07_errors Add lab 7 - Errors (#655) Nov 5, 2019
08_project Add lab 8 - Project Layout (#657) Nov 14, 2019
09_json Implement router with chi for puppy server Oct 5, 2019
10_rest Implement router with chi for puppy server Oct 5, 2019
11_notify Post lab11 fixes Nov 7, 2019
.gitignore 🌱 Create hello world, CI, coverage and linting setup (#1) Jan 29, 2019
.golangci.yml Implement router with chi for puppy server Oct 5, 2019
.travis.yml
LICENSE Add Apache 2.0 LICENSE (#13) Jan 31, 2019
README.md Update README.md badge URLs to new repo location May 9, 2019
cloudbuild.yaml Cloudbuild cleanup (#15) Feb 5, 2019
go.mod Lab11 - Puppy Notifiaction (#661) Oct 6, 2019
go.sum Lab11 - Puppy Notifiaction (#661) Oct 6, 2019
labs.md Update lab 08_project REAMDE.md Jun 24, 2019

README.md

Go Training

Build Status Coverage GolangCI

Go Course lab assignments repository.

Prerequisites

Build, execute, test, lint

Run the hello-world sample with

go run 00_hello_world/juliaogris/main.go

Alternative build and execute a binary with

go build -o hello_world ./00_hello_world/juliaogris
./hello_world

Test it with

go test ./...

Lint it with

golangci-lint run

Review coverage with

go test -coverprofile=coverage.out ./... && go tool cover -html=coverage.out

Pre-PR checklist

  • Ensure your source code changes
    • Build
    • Test
    • Lint
    • Have 100% test coverage
  • Ensure good commit messages
    • Separate subject from body with a blank line
    • Limit the subject line to 60 characters
    • Use the imperative mood in the subject line
    • Do not end the subject line with a period
    • Wrap the body at 80 characters
    • Use the body to explain what and why vs. how
    • Use git rebase -i COMMIT_HASH to rework your commits if necessary
  • Fill in PR description and reference an Issue for instance with #6
  • Review the "Files changed" section of your PR
  • "Think of the reviewer: your code needs to be reviewable and that should be a prime concern when writing your code, commits and PRs." (@camh-anz)
  • Review a colleague's PR and add a link to the review in your own PR description
You can’t perform that action at this time.