Skip to content

Gittensor Impact

Gittensor Impact #2

name: Gittensor Impact
on:
workflow_dispatch:
schedule:
- cron: "40 5 * * 1"
permissions:
contents: read
concurrency:
group: gittensor-impact
cancel-in-progress: false
jobs:
publish:
runs-on: ubuntu-latest
timeout-minutes: 10
# Scoped here rather than at workflow level (defense-in-depth): this is the
# only job that needs write access, to push SVG assets to the dedicated
# gittensor-impact-assets branch via matthewevans/gittensor-impact-action.
permissions:
contents: write
# matthewevans/gittensor-impact-action is a ~1.5-day-old repo; require a
# human approval before it runs with contents:write, on top of the SHA pin.
environment: gittensor-impact
steps:
- name: Generate and publish Gittensor impact card
uses: matthewevans/gittensor-impact-action@397fd470899cba47367458289a374eea9cb0d76a # main, 2026-07-06 (#1 per-repo API endpoint)
with:
title: Gittensory
# GitHub's release-asset uploads now reject re-uploads to an
# immutable release (HTTP 422), which the action's default
# release publish-mode hits every run. Branch mode force-pushes
# the SVGs to a dedicated orphan branch instead, sidestepping it.
publish-mode: branch