https://github.com/rolemodel/actions
Shared Github Actions
https://github.com/rolemodel/actions
Last synced: 4 months ago
JSON representation
Shared Github Actions
- Host: GitHub
- URL: https://github.com/rolemodel/actions
- Owner: RoleModel
- License: mit
- Created: 2025-02-18T21:34:59.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-08-26T21:58:24.000Z (10 months ago)
- Last Synced: 2025-08-27T06:12:01.347Z (10 months ago)
- Size: 15.6 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# RoleModel/actions
Shared Github Actions
## test-cleanup
Cleans up after test runs by uploading screenshots and dumping system information to stdout.
Inputs:
- `artifact-prefix`*: A string prefix to name the uploaded log file. Artifact name will be named `${artifact-prefix}-logs`
Example:
```yaml
- name: Cleanup
uses: RoleModel/actions/test-cleanup@v1
with:
artifact-prefix: rspec-system
```
## test-runtime-analyzer
Posts the runtime of the longest test files. This is important because the most granular parallel_tests goes is at
the file level, so when running in parallel, the entire suite can never be quicker than the slowest file.
Inputs:
- `test-output-path`*: Path to the test output file that hold runtimes
- `top-count`: Number of slowest tests to show. Default: 10
Example:
```yaml
- name: Analyze test runtimes
uses: RoleModel/actions/test-runtime-analyzer@v1
with:
test-output-path: tmp/turbo_rspec_runtime.log
```
## Shared workflow actions
This is a combination of three composite actions that can be used to run your entire CI flow for a rails app using parallel_tests. Each action allow you to customize the machine, environment variables, and any custom install steps that are needed. It does require you to check out the code yourself, since some install steps might happen after that.
The only inputs are for the linting and non system test action. Neither are required:
- `linting-step-required`: Boolean (default is false). Only needed if you have a linting command
- `linting-step-command`: String, `bundle exec rubocop --fail-level warning --display-only-fail-level-offenses --format github`
Here's what your `ci.yml` file could look like
```yaml
name: CI
on:
push:
branches: [ main, master ]
pull_request:
concurrency:
group: ${{ github.workflow }}-${{ github.event.pull_request.number }}-${{ github.event.ref }}
cancel-in-progress: true
env:
CI: true
RAILS_ENV: test
HONEYBADGER_SOURCE_MAP_DISABLED: true
POSTGRES_USER: postgres
POSTGRES_PASSWORD: password
SECRET_KEY_BASE: 0cb2b4ae6543f334e0eb5bc88bdabc24c9e5155ecb02a175c6f073a5a0d45a45f4a5b7d1288d3b412307bdfa19be441e97960ec4cd344f91f2d06a2595fb239c
jobs:
compile_assets:
name: Compile assets
runs-on: blacksmith-4vcpu-ubuntu-2204
timeout-minutes: 5
outputs:
cache-hit: ${{ steps.check-asset-cache.outputs.cache-hit }}
steps:
- name: Checkout code
uses: actions/checkout@v4
- uses: RoleModel/actions/compile-assets@v2
id: check-asset-cache
non-system-test:
name: Linting & Ruby Non-System Tests
runs-on: blacksmith-8vcpu-ubuntu-2204
timeout-minutes: 5
needs: compile_assets
services:
postgres:
image: postgres:16
ports:
- "5432:5432"
env:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: password
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Run shared flow
uses: RoleModel/actions/linting-and-non-system-tests@v2
with:
linting_step_required: true
linting_step_command: bundle exec rubocop --fail-level warning --display-only-fail-level-offenses --format github
system-test:
name: Ruby System Tests
runs-on: blacksmith-16vcpu-ubuntu-2204
timeout-minutes: 10
needs: compile_assets
services:
postgres:
image: postgres:16
ports:
- "5432:5432"
env:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: password
steps:
- name: Checkout code
uses: actions/checkout@v4
# allows for custom install steps between checkout & test run if needed
- name: Setup vips
run: |
sudo apt-get update
sudo apt-get install -y libvips
- name: Run shared flow
uses: RoleModel/actions/system-tests@v2
# if you've configured capybara to be compatible with the tmp:clear task
# you can tell the system-tests action like this:
with:
failure-screenshot-dir: tmp/screenshots
```
## Versioning
This is using [anothrNick/github-tag-action](https://github.com/anothrNick/github-tag-action/tree/master) to automatically
post version tags when a commit is merged to master. Unless you include `#patch` or `#major` in your commit message,
it will automatically create a new tag a minor version higher. `#none` will skip tagging altogether.