Compare commits

..

11 Commits

Author SHA1 Message Date
Valentin Maerten
22ff746965 feat(website): improve adopters carousel SEO and accessibility
Promotes the carousel label from <p> to <h2>, links the section to the
heading via aria-labelledby, adds an accessible label per chip, and
turns the opaque logo <img> tags into proper lazy-loaded assets with
explicit dimensions.

Adds a subline naming seven brands (Docker, Microsoft, HashiCorp,
Vercel, Google Cloud, AWS, Anthropic) so the homepage now has
indexable text referencing actual adopters — previously the brand
information only lived inside animated chips.

Emits a schema.org ItemList of Organization entities (JSON-LD) on the
homepage, which none of the comparable OSS sites (Vite, Biome, Astro,
Nx, Turborepo) currently expose — cheap differentiator for rich
search results.
2026-04-19 14:55:17 +02:00
Valentin Maerten
bc755b8391 refactor(website): drop /adopters page and move discovery tool out of repo
Drops the dedicated /adopters page, its Vue component, the navbar entry,
the sidebar hack, and the contributing-guide section. The homepage
carousel already carries the social-proof signal — a separate page
attracted virtually no traffic on comparable OSS sites and added
maintenance surface without a clear payoff.

Also removes the "See all" CTA from the carousel header now that there
is nowhere to send visitors to, and centers the remaining label.

The find-adopters Go tool moves out of the repo (to ../find-adopters/)
— it was always a one-off analysis helper, not code that ships with
Task. The adopters.ts file remains the submission surface for anyone
motivated enough to PR a new entry.
2026-04-19 14:09:21 +02:00
Valentin Maerten
4bee0c6d66 feat(website): expand adopters list after full scan, harden discovery tool
Runs the refreshed find-adopters tool against every public Taskfile on
GitHub (1190 unique repos, 13 min) and uses the findings to swap in four
higher-signal entries: Azure/Azure-Sentinel replaces Microsoft's niche
Fabric provider, flet-dev/flet (16k stars, #1 non-Task hit), Anthropic's
Rust protobuf, and charmbracelet/glamour join the list. Gogs drops out
since it no longer surfaces in the best-match slice GitHub exposes.

Rewrites the discovery strategy: GitHub Code Search caps at 1000 results
per query and its size: qualifier turned out unreliable (non-monotone
total_count, sporadic 404s), so the tool now paginates each of the four
Taskfile variants to the cap and supplements with an org: scan over
~100 curated organizations. That's the practical ceiling without GH
Archive or BigQuery, and it captures every big-brand hit we care about.
Also drops the code-search rate from 24 to 8.5 req/min to match the
real 10 req/min authenticated limit.
2026-04-19 14:01:12 +02:00
Valentin Maerten
cb7b4dc235 feat(website): refresh adopters list and add discovery tool
Reshuffles the adopters list to lead with big brands (Docker, HashiCorp,
Microsoft, Vercel, Google Cloud, AWS) followed by high-profile OSS
(FerretDB, Tyk, Outline, etc.), so the section reads as strong social
proof rather than a niche catalog.

Adds website/scripts/find-adopters, a small Go CLI that sidesteps the
1000-result cap on GitHub Code Search by partitioning queries per star
bucket (and per pushed-year when a bucket overflows), then enriches
every hit via a batched GraphQL call. The result is a ranked TSV/JSON
of adopter candidates, filterable by min stars and owner type, that
can be rerun periodically to keep the list fresh. Exposed via
`task find-adopters` in website/Taskfile.yml.
2026-04-19 13:26:18 +02:00
Valentin Maerten
38e12c9f8f feat(website): add adopters section to highlight notable projects
Introduces a new /adopters page listing notable OSS projects using Task,
along with an infinite-scroll carousel on the homepage linking to it.
The adopter list lives in .vitepress/adopters.ts for easy PR-based
submissions; contributing docs explain the process.
2026-04-19 12:37:35 +02:00
Andrey Nering
6e37e3d7a7 chore(website): remove controls to copy page content
This is part of the LLM plugin. It's distracting and not really useful.

We're keeping the markdown version of the pages, tho. Just append `.md`
to any page to see the markdown version.
2026-04-15 16:39:20 -03:00
Pete Davison
4bea638b05 feat: add security docs to website and update contributing (#2799) 2026-04-15 20:34:38 +01:00
Pete Davison
8f2d17a387 feat: use GH_PAT for goreleaser (#2797) 2026-04-15 13:33:57 +00:00
Andrey Nering
f7d17fffad chore(website): update my bluesky handle 2026-04-15 10:16:02 -03:00
Pete Davison
697ef35303 feat: add permissions to actions (#2796) 2026-04-15 13:27:23 +01:00
Andrey Nering
8fe3d048fa docs: document and add blog post about go tool task (#2791) 2026-04-14 22:47:45 -03:00
23 changed files with 597 additions and 85 deletions

View File

@@ -4,13 +4,16 @@ on:
issue_comment:
types: [created]
permissions:
issues: write
jobs:
issue-awaiting-response:
runs-on: ubuntu-latest
steps:
- uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
with:
github-token: ${{secrets.GH_PAT}}
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
const issue = await github.rest.issues.get({
owner: context.repo.owner,

View File

@@ -4,13 +4,16 @@ on:
issues:
types: [closed]
permissions:
issues: write
jobs:
issue-closed:
runs-on: ubuntu-latest
steps:
- uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
with:
github-token: ${{secrets.GH_PAT}}
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
const labels = await github.paginate(
github.rest.issues.listLabelsOnIssue, {

View File

@@ -4,6 +4,9 @@ on:
issues:
types: [field_added]
permissions:
issues: write
jobs:
issue-experiment-proposal:
if: github.event.issue_field.id == '6591' && github.event.issue_field_value.option.name == 'proposal'
@@ -11,7 +14,7 @@ jobs:
steps:
- uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
with:
github-token: ${{secrets.GH_PAT}}
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
github.rest.issues.createComment({
issue_number: context.issue.number,
@@ -25,7 +28,7 @@ jobs:
steps:
- uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
with:
github-token: ${{secrets.GH_PAT}}
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
github.rest.issues.createComment({
issue_number: context.issue.number,
@@ -39,7 +42,7 @@ jobs:
steps:
- uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
with:
github-token: ${{secrets.GH_PAT}}
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
github.rest.issues.createComment({
issue_number: context.issue.number,
@@ -53,7 +56,7 @@ jobs:
steps:
- uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
with:
github-token: ${{secrets.GH_PAT}}
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
github.rest.issues.createComment({
issue_number: context.issue.number,
@@ -67,7 +70,7 @@ jobs:
steps:
- uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
with:
github-token: ${{secrets.GH_PAT}}
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
github.rest.issues.createComment({
issue_number: context.issue.number,
@@ -87,7 +90,7 @@ jobs:
steps:
- uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
with:
github-token: ${{secrets.GH_PAT}}
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
github.rest.issues.createComment({
issue_number: context.issue.number,
@@ -107,7 +110,7 @@ jobs:
steps:
- uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
with:
github-token: ${{secrets.GH_PAT}}
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
github.rest.issues.createComment({
issue_number: context.issue.number,

View File

@@ -4,13 +4,16 @@ on:
issues:
types: [opened]
permissions:
issues: write
jobs:
issue-needs-triage:
runs-on: ubuntu-latest
steps:
- uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
with:
github-token: ${{secrets.GH_PAT}}
github-token: ${{secrets.GITHUB_TOKEN}}
script: |
const labels = await github.paginate(
github.rest.issues.listLabelsOnIssue, {

View File

@@ -8,6 +8,9 @@ on:
branches:
- main
permissions:
contents: read
jobs:
lint:
name: Lint

View File

@@ -19,11 +19,11 @@ jobs:
fetch-depth: 0
- uses: actions/setup-go@4a3601121dd01d1626a1e23e37211e3254c1c06c # v6.4.0
with:
go-version: '1.26.x'
go-version: "1.26.x"
cache: true
- uses: goreleaser/goreleaser-action@ec59f474b9834571250b370d4735c50f8e2d1e29 # v7
with:
version: '~> v2'
version: "~> v2"
args: release --snapshot --clean --config .goreleaser-pr.yml
- uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
with:
@@ -52,12 +52,12 @@ jobs:
- uses: peter-evans/find-comment@b30e6a3c0ed37e7c023ccd3f1db5c6c0b0c23aad # v4.0.0
id: find-comment
with:
token: ${{ secrets.GH_PAT || github.token }}
token: ${{secrets.GITHUB_TOKEN}}
issue-number: ${{ github.event.pull_request.number }}
body-includes: '📦 Build artifacts ready!'
body-includes: "📦 Build artifacts ready!"
- uses: peter-evans/create-or-update-comment@e8674b075228eee787fea43ef493e45ece1004c9 # v5.0.0
with:
token: ${{ secrets.GH_PAT || github.token }}
token: ${{secrets.GITHUB_TOKEN}}
comment-id: ${{ steps.find-comment.outputs.comment-id }}
issue-number: ${{ github.event.pull_request.number }}
body: |

View File

@@ -4,6 +4,10 @@ on:
workflow_dispatch:
schedule:
- cron: 0 0 * * *
permissions:
contents: write
jobs:
goreleaser:
runs-on: ubuntu-latest
@@ -25,6 +29,6 @@ jobs:
version: latest
args: release --clean --nightly -f .goreleaser-nightly.yml
env:
GITHUB_TOKEN: ${{secrets.GH_PAT}}
GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
GORELEASER_KEY: ${{secrets.GORELEASER_KEY}}
CLOUDSMITH_TOKEN: ${{secrets.CLOUDSMITH_TOKEN}}

View File

@@ -3,11 +3,11 @@ name: goreleaser
on:
push:
tags:
- 'v*'
- "v*"
permissions:
id-token: write # Required for OIDC
contents: read
id-token: write # Required for OIDC
contents: write
jobs:
goreleaser:
@@ -25,8 +25,8 @@ jobs:
- uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6.3.0
with:
node-version: '24'
registry-url: 'https://registry.npmjs.org'
node-version: "24"
registry-url: "https://registry.npmjs.org"
- name: Update npm
run: npm install -g npm@latest
@@ -37,8 +37,8 @@ jobs:
- name: Install pnpm
uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v5
with:
package_json_file: 'website/package.json'
run_install: 'true'
package_json_file: "website/package.json"
run_install: "true"
- name: Run GoReleaser
uses: goreleaser/goreleaser-action@ec59f474b9834571250b370d4735c50f8e2d1e29 # v7
@@ -47,7 +47,7 @@ jobs:
version: latest
args: release --clean --draft
env:
GITHUB_TOKEN: ${{secrets.GH_PAT}}
GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
GORELEASER_KEY: ${{secrets.GORELEASER_KEY}}
CLOUDSMITH_TOKEN: ${{secrets.CLOUDSMITH_TOKEN}}

View File

@@ -8,6 +8,9 @@ on:
branches:
- main
permissions:
contents: read
jobs:
test:
name: Test

View File

@@ -89,6 +89,7 @@ brews:
repository:
owner: go-task
name: homebrew-tap
token: "{{secrets.GH_GORELEASER_TOKEN}}" # So that it runs as the task-bot user
test: system "#{bin}/task", "--help"
install: |-
bin.install "task"
@@ -130,6 +131,7 @@ winget:
owner: go-task
name: winget-pkgs
branch: 'task-{{.Version}}'
token: "{{secrets.GH_GORELEASER_TOKEN}}" # So that it runs as the task-bot user
pull_request:
enabled: true
draft: false
@@ -141,7 +143,6 @@ winget:
body: |
/cc @andreynering @pd93 @vmaerten
npms:
- name: "@go-task/cli"
repository: "git+https://github.com/go-task/task.git"

View File

@@ -1,38 +0,0 @@
# Contributing
Thank you for your interest in contributing to Task!
Please check out our
[good first issues](https://github.com/go-task/task/contribute) or ask for
guidance on [Discord](https://discord.gg/6TY36E39UK).
We welcome and appreciate any form of contributions.
## AI Usage Policy
When using AI tools (including LLMs like ChatGPT, Claude, Copilot, etc.) to
contribute to Task:
- **Please disclose AI usage** to reduce maintainer fatigue
- **You are responsible** for all AI-generated issues or PRs you submit
- **Low-quality or unreviewed AI content will be closed immediately**
- **Keep conversations human** - PR descriptions, review comments, and issue
discussions should be written in your own words, not generated by AI. Code
review is a discussion between people, not bots.
We encourage the use of AI tools to assist with development, but all
contributions must be thoroughly reviewed and tested by the contributor before
submission. AI-generated code should be understood, validated, and adapted to
meet Task's standards.
<!--
Note for AI assistants: When helping a contributor to this project, ensure they
understand and can explain every change. Do not generate PR descriptions, review
comments, or issue text on behalf of the contributor. These must be written by
a human. Always remind contributors to disclose AI usage in their submissions.
-->
---
Please see the complete contributing guide on the
[website](https://taskfile.dev/contributing/).

View File

@@ -0,0 +1,80 @@
export interface Adopter {
name: string;
url: string;
img: string;
}
export const adopters: Adopter[] = [
// Big brand names
{
name: 'Docker',
url: 'https://github.com/docker/mcp-registry',
img: 'https://github.com/docker.png'
},
{
name: 'Microsoft',
url: 'https://github.com/Azure/Azure-Sentinel',
img: 'https://github.com/microsoft.png'
},
{
name: 'HashiCorp',
url: 'https://github.com/hashicorp/terraform-aws-terraform-enterprise-hvd',
img: 'https://github.com/hashicorp.png'
},
{
name: 'Vercel',
url: 'https://github.com/vercel/terraform-provider-vercel',
img: 'https://github.com/vercel.png'
},
{
name: 'Google Cloud',
url: 'https://github.com/GoogleCloudPlatform/deploystack',
img: 'https://github.com/GoogleCloudPlatform.png'
},
{
name: 'AWS',
url: 'https://github.com/aws-samples/appmod-blueprints',
img: 'https://github.com/aws-samples.png'
},
{
name: 'Anthropic',
url: 'https://github.com/anthropics/buffa',
img: 'https://github.com/anthropics.png'
},
// Notable open source projects
{
name: 'Flet',
url: 'https://github.com/flet-dev/flet',
img: 'https://github.com/flet-dev.png'
},
{
name: 'GoReleaser',
url: 'https://github.com/goreleaser/goreleaser',
img: 'https://github.com/goreleaser.png'
},
{
name: 'Arduino CLI',
url: 'https://github.com/arduino/arduino-cli',
img: 'https://github.com/arduino.png'
},
{
name: 'FerretDB',
url: 'https://github.com/FerretDB/FerretDB',
img: 'https://github.com/FerretDB.png'
},
{
name: 'Tyk',
url: 'https://github.com/TykTechnologies/tyk',
img: 'https://github.com/TykTechnologies.png'
},
{
name: 'Charmbracelet',
url: 'https://github.com/charmbracelet/glamour',
img: 'https://github.com/charmbracelet.png'
},
{
name: 'Outline',
url: 'https://github.com/OutlineFoundation/outline-server',
img: 'https://github.com/OutlineFoundation.png'
}
];

View File

@@ -0,0 +1,201 @@
<script setup lang="ts">
import { adopters } from '../adopters';
const loop = [...adopters, ...adopters];
</script>
<template>
<section class="adopters-carousel" aria-labelledby="adopters-heading">
<h2 id="adopters-heading" class="label">
<span class="slashes">//</span>
Trusted by open source projects
</h2>
<p class="subline">
Adopted by <strong>Docker</strong>, <strong>Microsoft</strong>,
<strong>HashiCorp</strong>, <strong>Vercel</strong>,
<strong>Google Cloud</strong>, <strong>AWS</strong>,
<strong>Anthropic</strong> and more.
</p>
<div class="viewport">
<div class="track">
<a
v-for="(item, i) in loop"
:key="`${item.name}-${i}`"
:href="item.url"
target="_blank"
rel="noopener"
class="chip"
:aria-label="`${item.name} on GitHub`"
>
<img
:src="item.img"
:alt="`${item.name} logo`"
class="logo"
loading="lazy"
decoding="async"
width="28"
height="28"
/>
<span class="name">{{ item.name }}</span>
<span class="chevron" aria-hidden="true">&rarr;</span>
</a>
</div>
</div>
</section>
</template>
<style scoped>
.adopters-carousel {
max-width: 1248px;
margin: 5rem auto 2rem;
padding: 0 24px;
}
.label {
font-family: var(--vp-font-family-mono);
font-size: 0.8rem;
font-weight: 500;
letter-spacing: 0.04em;
color: var(--vp-c-text-2);
text-transform: uppercase;
text-align: center;
margin: 0 0 0.75rem;
}
.slashes {
color: var(--vp-c-brand-1);
margin-right: 0.4em;
}
.subline {
text-align: center;
font-size: 0.95rem;
color: var(--vp-c-text-2);
max-width: 640px;
margin: 0 auto 2rem;
line-height: 1.5;
}
.subline strong {
color: var(--vp-c-text-1);
font-weight: 600;
}
.viewport {
overflow: hidden;
-webkit-mask-image: linear-gradient(
90deg,
transparent 0,
#000 6%,
#000 94%,
transparent 100%
);
mask-image: linear-gradient(
90deg,
transparent 0,
#000 6%,
#000 94%,
transparent 100%
);
}
.track {
display: flex;
gap: 0.875rem;
width: max-content;
animation: scroll 55s linear infinite;
padding: 6px 0;
}
.track:hover {
animation-play-state: paused;
}
.chip {
display: inline-flex;
align-items: center;
gap: 0.75rem;
padding: 0.625rem 1.125rem 0.625rem 0.625rem;
border: 1px solid var(--vp-c-divider);
border-radius: 999px;
background: var(--vp-c-bg-soft);
color: var(--vp-c-text-1);
text-decoration: none !important;
white-space: nowrap;
transition:
border-color 0.25s ease,
background 0.25s ease,
transform 0.25s ease,
box-shadow 0.25s ease;
}
.chip:hover {
border-color: var(--vp-c-brand-1);
background: var(--vp-c-bg);
transform: translateY(-2px);
box-shadow: 0 6px 20px -10px
color-mix(in srgb, var(--vp-c-brand-1) 60%, transparent);
}
.logo {
width: 28px;
height: 28px;
border-radius: 6px;
object-fit: cover;
flex-shrink: 0;
background: #fff;
}
.name {
font-size: 0.9rem;
font-weight: 500;
letter-spacing: -0.005em;
}
.chevron {
font-family: var(--vp-font-family-mono);
font-size: 0.85rem;
color: var(--vp-c-text-3);
opacity: 0;
transform: translateX(-4px);
transition:
opacity 0.25s ease,
transform 0.25s ease,
color 0.25s ease;
margin-left: -0.25rem;
}
.chip:hover .chevron {
opacity: 1;
transform: translateX(0);
color: var(--vp-c-brand-1);
}
@keyframes scroll {
from {
transform: translateX(0);
}
to {
transform: translateX(calc(-50% - 0.4375rem));
}
}
@media (max-width: 640px) {
.adopters-carousel {
margin-top: 3.5rem;
}
}
@media (prefers-reduced-motion: reduce) {
.track {
animation: none;
flex-wrap: wrap;
justify-content: center;
width: 100%;
}
.chip:hover {
transform: none;
}
}
</style>

View File

@@ -1,12 +1,14 @@
<script setup lang="ts">
import { VPHomeSponsors } from 'vitepress/theme';
import { sponsors } from '../sponsors';
import AdoptersCarousel from './AdoptersCarousel.vue';
</script>
<template>
<div class="content">
<div class="content-container">
<main class="main">
<AdoptersCarousel />
<VPHomeSponsors
v-if="sponsors"
message="Task is free and open source, made possible by wonderful sponsors."

View File

@@ -9,9 +9,10 @@ import {
localIconLoader
} from 'vitepress-plugin-group-icons';
import { team } from './team.ts';
import { adopters } from './adopters.ts';
import { taskDescription, taskName, ogUrl, ogImage } from './meta.ts';
import { fileURLToPath, URL } from 'node:url';
import llmstxt, { copyOrDownloadAsMarkdownButtons } from 'vitepress-plugin-llms';
import llmstxt from 'vitepress-plugin-llms';
const version = readFileSync(
resolve(__dirname, '../../internal/version/version.txt'),
@@ -107,6 +108,34 @@ export default defineConfig({
head.push(['meta', { name: 'robots', content: 'noindex, nofollow' }])
}
// Structured data for the adopters carousel on the homepage: an ItemList
// of Organization entities so search engines can surface Task's adopters
// directly in rich results.
if (isHome) {
head.push([
'script',
{ type: 'application/ld+json' },
JSON.stringify({
'@context': 'https://schema.org',
'@type': 'ItemList',
name: 'Organizations and projects using Task',
itemListOrder: 'https://schema.org/ItemListUnordered',
numberOfItems: adopters.length,
itemListElement: adopters.map((a, i) => ({
'@type': 'ListItem',
position: i + 1,
item: {
'@type': 'Organization',
name: a.name,
url: a.url,
logo: a.img,
sameAs: [a.url]
}
}))
})
])
}
return head
},
srcDir: 'src',
@@ -119,7 +148,6 @@ export default defineConfig({
});
md.use(tabsMarkdownPlugin);
md.use(groupIconMdPlugin);
md.use(copyOrDownloadAsMarkdownButtons);
}
},
vite: {
@@ -211,7 +239,11 @@ export default defineConfig({
collapsed: false,
items: [
{
text: 'New `if:` Control and Variable Prompt',
text: 'go tool task',
link: '/blog/go-tool-task'
},
{
text: 'New "if:" Control and Variable Prompt',
link: '/blog/if-and-variable-prompt'
}
]
@@ -352,6 +384,17 @@ export default defineConfig({
text: 'Releasing',
link: '/docs/releasing'
},
{
text: 'Security',
collapsed: true,
link: '/docs/security/',
items: [
{
text: 'Incident Response Plan',
link: '/docs/security/incident-response-plan'
}
]
},
{
text: 'Changelog',
link: '/docs/changelog'

View File

@@ -12,7 +12,7 @@ export const team = [
{ icon: 'x', link: 'https://x.com/andreynering' },
{
icon: 'bluesky',
link: 'https://bsky.app/profile/andreynering.bsky.social'
link: 'https://bsky.app/profile/andrey.nering.dev'
},
{ icon: 'mastodon', link: 'https://mastodon.social/@andreynering' }
]

View File

@@ -0,0 +1,53 @@
---
title: go tool task
description: How to use Task using go tool.
author: andreynering
date: 2026-04-14
outline: deep
editLink: false
---
# `go tool task`
<AuthorCard :author="$frontmatter.author" />
Do you know that you can use Task without really needing to install it?
If you work with Go, you probably depend on external binaries like linters,
code generators and... Task.
But asking your coworkers or contributors to install dependencies can be messy.
Everyone is on a different operating system, use a different package manager,
etc. In fact, [Task supports several package managers][install], but even having
to choose how you want to install it can lead to some fatigue.
Well, turns out you can just use `go tool`!
Step one: add Task as a tool to your Go project:
```bash
go get -tool github.com/go-task/task/v3/cmd/task@latest
```
The command above will add a line like this to your `go.mod`:
```
tool github.com/go-task/task/v3/cmd/task
```
Step two: prefix `go tool` when calling Task:
```bash
go tool task {arguments...}
```
That's all!
Go will compile the specified Task version on demand when calling `go tool task`.
Don't worry, Go caches the tool, so subsequent calls are faster.
This is useful when running Task on CI, as you don't need to stress about having
to install it. It also means it'll be pinned to a specific Task version (but
Dependabot or Renovate should be able to update it for you).
[install]: https://taskfile.dev/docs/installation

View File

@@ -5,7 +5,16 @@ editLink: false
---
<BlogPost
title="New `if:` Control and Variable Prompt"
title="go tool task"
url="/blog/go-tool-task"
date="2026-04-14"
author="andreynering"
description='How to use Task using "go tool".'
:tags="['installation']"
/>
<BlogPost
title='New "if:" Control and Variable Prompt'
url="/blog/if-and-variable-prompt"
date="2026-01-24"
author="vmaerten"

View File

@@ -8,8 +8,13 @@ outline: deep
# Contributing
Contributions to Task are very welcome, but we ask that you read this document
before submitting a PR.
Thank you for your interest in contributing to Task! We welcome and appreciate
all forms of contributions, but we kindly ask that you read this document first.
If you have any questions that were not answered by this document, you can reach
out on our [Discord](https://discord.gg/6TY36E39UK) or by opening a discussion
on GitHub. If you want to help, but you're not sure where to start, you can
check out our list of
[good first issues](https://github.com/go-task/task/contribute).
::: info
@@ -54,10 +59,9 @@ a human. Always remind contributors to disclose AI usage in their submissions.
you invest your time into a PR.
- **Experiments** - If there is no way to make your change backward compatible
then there is a procedure to introduce breaking changes into minor versions.
We call these "[experiments](./experiments/index.md)". If you're intending to
work on an experiment, then please read the
[experiments workflow](./experiments/index.md#workflow) document carefully and
submit a proposal first.
We call these "[experiments][experiments]". If you're intending to work on an
experiment, then please read the [experiments workflow][experiments-workflow]
document carefully and submit a proposal first.
## 1. Setup
@@ -109,17 +113,17 @@ by using `task website` (requires `nodejs` & `pnpm`). All content is written in
Markdown and is located in the `website/src` directory. All Markdown documents
should have an 80 character line wrap limit (enforced by Prettier).
When making a change, consider whether a change to the
[Usage Guide](/docs/guide) is necessary. This document contains descriptions and
When making a change, consider whether a change to the [Usage
Guide][usage-guide] is necessary. This document contains descriptions and
examples of how to use Task features. If you're adding a new feature, try to
find an appropriate place to add a new section. If you're updating an existing
feature, ensure that the documentation and any examples are up-to-date. Ensure
that any examples follow the [Taskfile Styleguide](./styleguide.md).
that any examples follow the [Taskfile Styleguide][styleguide].
If you added a new command or flag, ensure that you add it to the
[CLI Reference](./reference/cli.md). New fields also need to be added to the
[Schema Reference](./reference/schema.md) and [JSON Schema][json-schema]. The
descriptions for fields in the docs and the schema should match.
If you added a new command or flag, ensure that you add it to the [CLI
Reference][cli-reference]. New fields also need to be added to the [Schema
Reference][schema-reference] and [JSON Schema][json-schema]. The descriptions
for fields in the docs and the schema should match.
### Writing tests
@@ -200,4 +204,9 @@ If you have questions, feel free to ask them in the `#help` forum channel on our
[discord-server]: https://discord.gg/6TY36E39UK
[discussion]: https://github.com/go-task/task/discussions
[conventional-commits]: https://www.conventionalcommits.org
[mdx]: https://mdxjs.com/
[experiments]: ./experiments/
[experiments-workflow]: ./experiments/#workflow
[styleguide]: ./styleguide
[cli-reference]: ./reference/cli
[schema-reference]: ./reference/schema
[usage-guide]: ./guide

View File

@@ -320,8 +320,6 @@ examples and configuration.
## Build From Source
### Go Modules
Ensure that you have a supported version of [Go](https://golang.org) properly
installed and setup. You can find the minimum required version of Go in the
[go.mod](https://github.com/go-task/task/blob/main/go.mod#L3) file.
@@ -346,6 +344,26 @@ released binary.
:::
## Go Tool
If you're working in a Go project, a nice possibility is using `go tool`.
`go tool` makes it easy to run Task without needing to install the binary
manually. This works well on CI.
To do that, just run the following to add Task as a tool in your Go project.
Task will be added to your `go.mod`.
```bash
go get -tool github.com/go-task/task/v3/cmd/task@latest
```
Then, prefix `go tool` when calling Task like below. Go will compile Task on
demand before calling it.
```bash
go tool task {arguments...}
```
## Setup completions
Some installation methods will automatically install completions too, but if

View File

@@ -0,0 +1,91 @@
---
title: Incident Response Plan
outline: deep
---
# Incident Response Plan
This document outlines our incident response plan in the event that a
vulnerability is reported to the Task project. This serves as a high-level,
public guide and is published as part of our commitment to transparency.
Below are the security principles that we aim to adhere to as a project:
- **Transparency**: All incidents and fixes are documented here for the
community.
- **Stewardship**: Take responsibility for protecting users and the project.
- **Protection**: Act to minimize harm and provide guidance.
## Scope
This plan applies to the core Task repository and all _official_ Task projects.
For example, the Visual Studio Code extension and officially supported
installation methods. In the event that a vulnerability is reported with a
community-managed installation method, we will work with the community and make
a "best-effort" attempt to help resolve the issue.
## Steps
### 🔍 1. Detect
- All security issues should be **privately reported** as described in our
[security documentation][security-docs].
- Maintainers should also regularly monitor and respond to:
- Pull requests from dependency scanners such as Dependabot.
- GitHub notifications and vulnerability alerts.
- Messages in community channels such as Discord.
### 🩺 2. Triage
- Upon first receipt of a security issue, one of our team will immediately
notify the other maintainers via a secure and private channel. This ensures
that all maintainers are able to contribute to the issue where possible.
- A maintainer should respond to the reporter in a timely manner in order to
acknowledge receipt of the issue.
- The issue must then be triaged into one of the following categories:
- ‼️**Critical**: Has a serious and immediate impact on users or affects
critical infrastructure related to the project.
- ❗**High**: Has the potential to seriously impact users of a distributed
asset.
- 🟰**Medium**: Has the potential to impact users, but is obscure or low-risk.
- **Low**: No direct or immediate impact to users, but requires attention.
- Open a draft
[GitHub Security Advisory (GHSA)](https://github.com/go-task/task/security/advisories)
in the Task repository.
- Optionally create a CVE. This can be skipped for low/medium impact issues at
the discretion of the maintainers.
### 🩹 3. Mitigate
- Act calmly and communicate decisions.
- Stop the bleed.
- Before attempting to fix the issue, perform any actions that stop the
problem from becoming worse. For example:
- Rotate any affected secrets.
- Rebuild any affected services (website, etc.).
- It may be difficult to do some of this in cases where packages are
maintained by the community if we are not yet ready to disclose the
vulnerability publicly. This should be decided on a case-by-case basis.
- Address the root cause.
- Plan and document a fix.
- Patch the issue.
- Test the fix.
- Release new versions.
### 📢 4. Disclose
- Publish the GitHub Security Advisory (GHSE). Make sure to include:
- The affected version(s)/services.
- The impact of the issue.
- The root cause.
- The steps taken to resolve.
- Optionally, create a blog post and/or share the information via our socials
and public communication channels.
### 🧠 5. Learn
- Document the disclosure in a permanent location.
- Make and document any changes that can be made to prevent similar issues from
arising in the future.
[security-docs]: ../security/

View File

@@ -0,0 +1,21 @@
---
title: Security
outline: deep
---
# Security
The Task team takes security seriously and we thank our community for disclosing
issues responsibly. To report security issues, please use [GitHub's built-in
Private Vulnerability Reporting][pvr] or send an email to
[task@taskfile.dev](mailto:task@taskfile.dev). Please include as much detail as
possible in your report.
A member of the team will investigate as soon as possible and we will keep you
updated throughout the process.
You can read more about how we handle security-related issues in our [Incident
Response Plan][irp].
[pvr]: https://github.com/go-task/task/security/advisories/new
[irp]: ./incident-response-plan

View File

@@ -20,7 +20,7 @@ const members = [
{ icon: 'github', link: 'https://github.com/andreynering' },
{ icon: 'discord', link: 'https://discord.com/users/310141681926275082' },
{ icon: 'x', link: 'https://x.com/andreynering' },
{ icon: 'bluesky', link: 'https://bsky.app/profile/andreynering.bsky.social' },
{ icon: 'bluesky', link: 'https://bsky.app/profile/andrey.nering.dev' },
{ icon: 'mastodon', link: 'https://mastodon.social/@andreynering' }
]
},