Is your feature request related to a problem? Please describe.

Following the guidance of github, many developers are moving to main as their default branch. Saving developers from the very small hindrance of using DEFAULT_BRANCH: main would contribute to smoothing the transition.

Describe the solution you'd like

The default branch should be main. If it does not exist, use `m

Brett Fox's answer to When VCs say the giants will enter the market and put you out of business in a day, what is the best answer you can give? - Quora





July 19, 2019 at 01:27PM

via Instapaper https://ift.tt/32B5pTS

Currently certain PR's coming from forks result in the action running in the context of the fork, which means it can't post a comment or a PR review to the PR/issue.

Possible workarounds:

1. Report the size table back using a Status Check
   • Not sure if GitHub's UI will handle

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']

I am not sure if this belongs here, but I am having an issue when using this Github Action.

This is the link to the github run that failed:
https://github.com/jampp/migratron/pull/25/checks?check_run_id=456554120

and the content is:

Uploading distributions to https://test.pypi.org/legacy/
Uploading migratron-1.1.0-py3-none-any.whl

  0%|          | 0.00/30.5k [00:00<?, ?B/s]
100%|