Automation by GitHub Actions

Automation

Automatically trigger build and test for push and pull_request.

Action	Description
osrm-backend CI	`cpp` build on both `linux` and `macosx`, will have unittests later.
Go CI	`Go` build and test check.

Automatically build and publish docker image if anything changed on any branch.
Refer to Docker Image Tags Rule and Images on DockerHub to find your images.

Action	Description
Build Docker - osrm-backend-dev	Build and publish `telenavmap/osrm-backend-dev` docker image if anything changed on any branch.
Build Docker - osrm-backend	Build and publish `telenavmap/osrm-backend` docker image if anything changed on any branch.

Automatically build and release docker images/binaries when create new release on GitHub Release page.

Action	Description
Release Docker - osrm-backend-dev	Release `telenavmap/osrm-backend-dev` docker only if tag created with `osrm-backend-dev/` prefix. Refer to Docker Image Tags Rule and Images on DockerHub to find the released images.
Release Docker - osrm-backend	Release `telenavmap/osrm-backend` docker only if tag created with `osrm-backend/` prefix. Refer to Docker Image Tags Rule and Images on DockerHub to find the released images.
- Release cmd/osrm-files-extractor - Release cmd/trafficproxy-cli - Release cmd/oasis	Release widely use binaries then people can easy to get. Find the released binaries on GitHub Release Assets.

For Build Docker - osrm-backend-dev and Build Docker - osrm-backend,
- ${BRANCH_BASENAME}-${GIT_SHA_FIRST_7}-${DATE}: E.g., telenavmap/osrm-backend-dev:action-osrm-backend-dev-f41a955-20200303.
- If it's triggered on master, the latest tag will also be updated.
For Release Docker - osrm-backend-dev and Release Docker - osrm-backend,
- ${GIT_TAG_BASENAME}: E.g., osrm-backend-dev/v1.0 will generate telenavmap/osrm-backend-dev:v1.0.
- The latest tag will always be updated for releases.