starter-workflows

T

Chris Sidi a33d16cad6 Use separate steps for install, build and test (#192 )

* Use separate steps for install, build and test

Having separate steps makes it easier to determine what failed.

Switching from `npm ci` to `npm install` because the Windows image uses node v8.10.0 and npm v5.6.0. `ci` was introduced in npm v5.7.0.

See https://github.com/actions/virtual-environments/issues/88

* Remove `name`

2019-11-12 11:06:49 -05:00

.github

Change relative link to fully qualified link.

2019-11-01 22:57:48 -04:00

automation

Fix TYPO in the comment block

2019-10-18 15:51:16 +02:00

Use separate steps for install, build and test (#192 )

2019-11-12 11:06:49 -05:00

icons

Add Swift starter template

2019-08-29 14:21:24 +07:00

CONTRIBUTING.md

Update CONTRIBUTING.md

2019-10-01 13:57:51 -07:00

LICENSE

Update LICENSE

2019-07-30 10:09:41 -07:00

README.md

Improve the readme

2019-08-27 15:35:20 -07:00

README.md

Starter Workflows

These are the workflow files for helping people get started with GitHub Actions.

Directory structure:

ci: solutions for Continuous Integration
automation: solutions for automating workflows.
icons: svg icons for the relevant template

Each workflow must be written in YAML and have a .yml extension. They also need a corresponding .properties.json file that contains extra metadata about the workflow (this is displayed in the GitHub.com UI).

For example: ci/python-django.yml and ci/python-django.properties.json.

Valid properties:

name: the name shown in onboarding
description: the description shown in onboarding
iconName: the icon name in the relevant folder, for example django should have an icon icons/django.svg. Only SVG is supported at this time
categories: the categories that it will be shown under