Koskamo
Navigation

GitHub Actions best practices

Source-linked guidance on GitHub Actions: workflow triggers and schedules, runner selection, dependency caching, secrets and environments, and security hardening. Scoped to GitHub Actions; not a general CI/CD corpus.

Browse 5 documentsUse with your agent

Documents

Showing 1–5 of 5 documents

DocumentVersion

Choosing runners with runs-on

Use jobs.<job_id>.runs-on to define the machine a job runs on: a GitHub-hosted runner, a larger runner, or a self-hosted runner. Runners are targeted by labels, group membership,…

v1

Dependency caching with actions/cache

actions/cache (actions/cache@v4) restores a cache by exact key match, then partial key matches, then restore-keys checked sequentially for partial matches; on a partial match the…

v1

Secrets at repository, environment, and organization level

Create secrets at the repository, environment, or organization level; in organization repositories this requires admin access. Organization secrets carry an access policy — all…

v1

Security hardening: script injection and third-party actions

Against script injection, prefer a JavaScript action that receives the context value as an argument instead of an inline script; when an inline script must handle untrusted…

v1

Workflow triggers and scheduled runs

Workflow triggers are the events that cause a workflow to run: activity on GitHub, a scheduled time, or an external event, and not all webhook events trigger workflows. Many…

v1

Source, review, and usage
Published on Koskamo by
Koskamo editorial
Version
1
Documents
5 documents
Reviewed
2026-10-04
Agent lookups
0 in the last 90 days
Reuse
Original summaries; linked sources retain their own terms.
Review status
Maintained with the application; source links supplied

Original sources are linked on each document. Owner approval records a publishing decision; it does not imply independent fact checking.

Use this dataset from an agent

Agents can query it without an account. POST to /api/v1/retrieve, or connect an MCP client and call koskamo_retrieve with dataset: "github-actions-best-practices".

Set up your agentRead documents as JSON

The JSON endpoint returns document text and source links in pages. Use limit and offset to retrieve more records; total gives the dataset size.

retrieve request
curl --fail-with-body 'https://koskamo.com/api/v1/retrieve' -H 'Content-Type: application/json' --data-raw '{"query":"github-actions-best-practices","dataset":"github-actions-best-practices","top_k":3}'

Change history

This dataset is maintained with the application. Its history is the Koskamo release history; the review date above is when its sources were last checked.