Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Latest commit

 

History

History
History

README.md

Outline

GitHub Workflows

Please use the following naming convention such that we can easily map failed builds back to YAML files here in the repository.

$number-$friendlyname-$environment-$testcommands

Where number is just a unique identifier to easily map failed builds to YAML files. See below for more guidance on choosing a number. Where friendlyname is a good descriptor to describe what is being checked (avoid words like "build" or "main" as they are too generic) Where environment describes the environment it is running in, such as alpine:latest or armv7. Where testcommands are the commands that a user can replicate on their computer! Do NOT test commands that can not be easily replicated!

007-linter-alpine-make-lint.yaml

A new linter running in alpine that tests the command make lint and 007 can easily be mapped backed to the file.

Choosing a number

  • 001-099: Reserved for workflows that don't use a container image

Testing workflows

Workflows can be testing using the tool act. You'll need to install that locally, then you can run commands to test each file individually, locally:

make ci-local file=001-tester-ubuntu-make-test.yml

Morty Proxy This is a proxified and sanitized view of the page, visit original site.