These are some notes about features provided by GitHub Actions that may be useful for us:
For example, you can have your workflow run on push events to master and release branches or, only run on pull_request events that target the master branch or, run every day of the week from Monday - Friday at 02:00.
GitHub actions provides hosted runners for Linux, Windows and macOS. To change the operating system for you job simply specify a different virutal machine. The available virtual machine types are:
ubuntu-latest, ubuntu-18.04, or ubuntu-16.04
windows-latest, windows-2019, or windows-2016
macOS-latest or macOS-10.14
You can run workflows directly on the virtual machine or in a Docker container.
Each job in a workflow executes in a fresh instance of the virtual environment. All steps in the job execute in the same instance of the virtual environment, allowing the actions in that job to share information using the filesystem.
With the matrix strategy GitHub Actions can automatically run your jobs across a set of different values of your choosing.
GitHub Actions supports conditions on steps and jobs based data present in your workflow context. To run a step only as part of a push and not in a pull_request you simply specify a condition in the if: property based on the event name.
Artifacts are the files created when you build and test your code. For example, artifacts might include binary or package files, test results, screenshots, or log files. When a run is complete, these files are removed from the virtual environment that ran your workflow and archived for you to download.
These are some notes about features provided by GitHub Actions that may be useful for us:
https://help.github.com/en/articles/events-that-trigger-workflows
https://help.github.com/en/articles/virtual-environments-for-github-actions
https://help.github.com/articles/workflow-syntax-for-github-actions#jobsjob_idstepsif
https://help.github.com/en/articles/managing-a-workflow-run#downloading-logs-and-artifacts
For end users:
For issues: