Gain insights into writing professional command-line programs in Go. Delve into structuring Go programs, writing idiomatic code, testing effectively, and impressing users and managers.

write professional command  - line programs in Go.png

data.tar.gz

Go run main.go

Run main.sh

Run go test

Run go test2

GoLive

GoLiveTesting

Multi-git-Custom

Pre+main-v0.2

Main_to_cmd

Run go test-Coverage

Ginkgo

Ginkgo-BDD

Ginkgo-e2e

Cobra

Cobra-NoInstall

Cobra-NoInstall-FullApp

Final_Cobra_Multi-git

Viper

Viper-etcd

Viper-Cobra

SelfUpdating

Make

Special build

Embedding_Data

Go run main.go-Simple

In this course you will learn why Go is an awesome language for writing command-line programs. You will learn how to structure your Go programs, how to write idiomatic Go code, how to test your programs and how to amaze your users, peers and managers. 

The focus is on command-line programs in order to keep the course down to earth, but most of the principles and best practices you will learn apply to any Go program.

Write Professional Command-line Programs in Go

## CI/CD pipeline for multi-git

Let's start with a basic pipeline that builds the binary and runs the unit tests. Note that running the end-to-end tests is a little bit challenging in the GitHub Actions environment, so we will leave it out for now.

GitHub Actions workflows are YAML files that are defined in your repo's .github/workflows directory. I defined two workflows:

```
(🐙)/multi-git/
$ tree .github
.github
└── workflows
    ├── on-push.yml
    └── on-tag-push.yml

1 directory, 2 files
``` 

The `on-push.yml` workflow is triggered every time a commit is pushed. The `on-tag-push.yml`  workflow is called whenever a tag is pushed. Here is what it looks like on GitHub:




# CI/CD pipeline for multi-git

Let's start with a basic pipeline that builds the binary and runs the unit tests. Note that running the end-to-end tests is a little bit challenging in the GitHub Actions environment, so we will leave it out for now.

GitHub Actions workflows are YAML files that are defined in your repo's .github/workflows directory. I defined two workflows:

```
(🐙)/multi-git/
$ tree .github
.github
└── workflows
    ├── on-push.yml
    └── on-tag-push.yml

1 directory, 2 files
``` 

The `on-push.yml` workflow is triggered every time a commit is pushed. The `on-tag-push.yml`  workflow is called whenever a tag is pushed. Here is what it looks like on GitHub:




Let's take advantage of GitHub Actions and create a CI/CD pipeline to build multi-git and run its tests.

Making a CI/CD Pipeline for multi-git

Overview

Restructuring multi-git

Testing 1,2,3...

Adding Smart Command-Line Parsing

Adding Advanced Configuration

Adding Bells and Whistles

Summary

Making a CI/CD Pipeline for multi-git

CI/CD pipeline for multi-git