Skip to content
1mb-devPublic

About

Shared workflows and org-level defaults for 1mb-dev

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

37 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

.github

Shared workflows and org-level defaults for 1mb-dev.

Reusable Workflows

ci-go.yml -- Go CI

Lint, test, security scan, and build for Go projects.

# In your repo's .github/workflows/ci.yml
name: CI
on: [push, pull_request]
jobs:
  ci:
    uses: 1mb-dev/.github/.github/workflows/ci-go.yml@main

Inputs (all optional):

Input Default Description
go-versions ["1.26", "1.27"] Go versions to test against
lint-go-version "1.26" Go version for linting
golangci-lint-version v2.9.0 golangci-lint version
coverage-threshold 0 Min coverage % (0 = skip)
run-security true Run govulncheck
run-secret-scan true Run gitleaks via secret-scan.yml
build-binary "" Main package path (empty = skip)

ci-node.yml -- Node/TS CI

Lint, test, build, and security audit for Node.js/TypeScript projects.

name: CI
on: [push, pull_request]
jobs:
  ci:
    uses: 1mb-dev/.github/.github/workflows/ci-node.yml@main

Inputs (all optional):

Input Default Description
node-versions ["22", "24"] Node versions to test against
lint-node-version "24" Node version for linting
run-audit true npm audit --omit=dev --audit-level=high blocks; the full-tree audit reports to the job summary without blocking
run-secret-scan true Run gitleaks via secret-scan.yml
run-build true Run npm run build

secret-scan.yml -- Gitleaks secret scan

Scans the repository for committed secrets using gitleaks. Called transitively by ci-go.yml and ci-node.yml when run-secret-scan is true; can also be invoked directly for repos that do not use the language CIs.

name: Secret scan
on: [push, pull_request]
jobs:
  scan:
    uses: 1mb-dev/.github/.github/workflows/secret-scan.yml@main

Inputs (all optional):

Input Default Description
gitleaks-version 8.30.1 Gitleaks binary version
gitleaks-sha256 (pinned for the default) sha256 of the linux_x64 tarball. Required when gitleaks-version is overridden; the job fails closed without it

The job fails on any detected secret (--exit-code 1). Findings are redacted in logs.

dependabot-auto-merge.yml -- Auto-merge Dependabot PRs

Auto-merges patch and minor dependency updates when CI passes.

name: Dependabot auto-merge
on: pull_request
jobs:
  auto-merge:
    uses: 1mb-dev/.github/.github/workflows/dependabot-auto-merge.yml@main

Prerequisite: Enable "Allow auto-merge" in repo settings.

release.yml -- Tag-driven release

Creates a GitHub release when a version tag is pushed. Title resolution falls through three sources in order: annotated tag message subject, next unused name from .github/release-names.txt (per-repo theme), or the tag itself.

# In your repo's .github/workflows/release.yml
name: Release
on:
  push:
    tags: ['v*']
jobs:
  release:
    uses: 1mb-dev/.github/.github/workflows/release.yml@main

Inputs (all optional):

Input Default Description
draft true Create as draft (false to publish immediately)

Adding a per-repo .github/release-names.txt (one name per line) enables themed release titles assigned in file order.

Required Check

Rulesets on consumer repos require ci / CI Result (both ci-go.yml and ci-node.yml emit it). It needs every job, so a red Security or Lint blocks the merge; a job disabled by its input (run-security: false, empty build-binary) passes. Do not require ci / Test Result: it covers only the test matrix and is kept until existing branch protection moves off it.

Pinning Policy

All shared workflows are consumed via @main. This is intentional: a single maintainer plus a small consumer set means fix-once-apply-everywhere is the whole point. Every commit on .github/main propagates to all consumers on their next workflow run.

Trade-off: there is no version-pin shock absorber. Breaking changes hit all repos at once. Mitigations: (a) keep shared workflows minimal and stable, (b) consult CHANGELOG.md before merging non-trivial changes, (c) revisit pinning if consumer count grows past ~30 or shared workflows start breaking on bumps.

Org Profile

profile/README.md is displayed on the 1mb-dev org page. It adapts the 1mb.dev cover and names no repos; GitHub's popular and full repository lists carry them.

About

Shared workflows and org-level defaults for 1mb-dev

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages