deploy

hi there,

Just installed latest versions of shipit packages and here's something new:

Running 'deploy:fetch' task...
Create workspace...
Workspace created: "/var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Ro"
Initialize local repository in "/var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Ro"
Running "git init" on local.
@ Initialized empty Gi

Hello,

I believe having type hints would really improve this project.
I offer that from now on type hints are selected as a necessary condition for the upcoming changes in PRs.
This way code base would slowly converge to a type hinted one.

Also this issue could be tagged as a good first issue for volunteer collaborators :)

cc: @abidlabs

Ref:
https://docs.python.org/3/library/typing

From google/ko#530 (comment)

A few points to note:

• The -B (--base-import-paths) and --bare flags are not designed to be used together, and in this case, -B takes precedence: https://github.com/google/ko#naming-images

• The main field in .ko.yaml is a directory, not a full Go import path.

• If your .ko.yaml and `go.mod

(suggested by Berndinox in #205; been bugging me for a while too)

Currently, the Docker image exposes port 80. We should change this so that running Meli doesn't require root access.

We'll need to update the deployment docs.

Only a subset of the inputs documented are actually allowed in the action.yml, resulting in the following warning when I use customParameters, versioning, and other parameters:

##[warning]Unexpected input 'customParameters', valid inputs are ['unityVersion', 'targetPlatform', 'projectPath', 'buildName', 'buildsPath', 'buildMethod']