* Workaround for repeated invocations
As noted in the comment, repeated invocations of this action might have
caused environment variables to overflow. This cute hack avoid this,
allowing to reconfigure environment.
* Note caveats in README
While this approach mostly works, I still have reservations so let's
leave some cautionary notes.
* Test repeated reconfiguration on CI
Well, let's build our "Hello, world!" four times, for four different
architectures, because why not.
* Use newer actions/checkout@v2 in examples
That's the current version. Even our own build scripts use it.
* Correct actions syntax
By the way, it's been ages since steps get their own section...
* Provide an example with matrix
Finally, have some example to showcase input usage.
* Move inputs after examples
Since they are more useful, put copy-pastable examples first. Then you
can look at all available inputs, now that you know how to use them.
By a public request, let's support aliases for architecture parameters.
Treat "arch: Win32" as "x86" and "Win64" as "x64".
Test this on CI just in case x86 breaks or something.
Now that I know how to write some simple action, let's make a stub
more complete. For example, I already know what inputs I would like
to handle for this action.
Alexei Lozovsky