cargo-install/.github/workflows/ci.yml

name: CI

on:
  push:
    branches: [master]
  pull_request:
  workflow_dispatch:
  schedule: [cron: "40 1 * * *"]

permissions:
  contents: read

jobs:
  install:
    name: Install
    runs-on: ubuntu-latest
    timeout-minutes: 45
    steps:
      - uses: actions/checkout@v4
      - uses: ./
        with:
          crate: cargo-outdated
      - run: cargo outdated --version
Add a basic daily CI job 2022-06-26 21:52:47 -07:00			`name: CI`

			`on:`
			`push:`
			`branches: [master]`
			`pull_request:`
Support a manual trigger on all workflows 2023-02-18 17:17:51 -08:00			`workflow_dispatch:`
Add a basic daily CI job 2022-06-26 21:52:47 -07:00			`schedule: [cron: "40 1 * * *"]`

GitHub Workflows security hardening 2022-09-02 15:09:29 -07:00			`permissions:`
			`contents: read`

Add a basic daily CI job 2022-06-26 21:52:47 -07:00			`jobs:`
			`install:`
Fix name of CI job 2024-04-14 10:12:12 -07:00			`name: Install`
Add a basic daily CI job 2022-06-26 21:52:47 -07:00			`runs-on: ubuntu-latest`
Time out workflows after 45 minutes GitHub's default timeout is 6 hours. Recently some of my GitHub Actions jobs have started randomly stalling for that long, which is inconvenient because it ties up a chunk of my runner quota. It apepars to be very rare for a job to recover after stalling. It's better to time out quicker and retry on a different runner. 2022-11-24 21:35:28 -08:00			`timeout-minutes: 45`
Add a basic daily CI job 2022-06-26 21:52:47 -07:00			`steps:`
Update actions/checkout@v3 -> v4 2023-09-04 22:34:58 -07:00			`- uses: actions/checkout@v4`
Add a basic daily CI job 2022-06-26 21:52:47 -07:00			`- uses: ./`
			`with:`
			`crate: cargo-outdated`
			`- run: cargo outdated --version`