Skip to content

build(deps): declare ourself as a 'go tool' for ourself#2785

Closed
dolmen wants to merge 1 commit into
go-task:mainfrom
dolmen-go:declare-as-tool-in-our-own-Go-module
Closed

build(deps): declare ourself as a 'go tool' for ourself#2785
dolmen wants to merge 1 commit into
go-task:mainfrom
dolmen-go:declare-as-tool-in-our-own-Go-module

Conversation

@dolmen
Copy link
Copy Markdown

@dolmen dolmen commented Apr 12, 2026

In go.mod declare ourself as a tool for our own consumption.

$ go get -tool ./cmd/task

Task developers can now run tasks via go tool task, independently of the task installed in $PATH.

This is a first step before further experiments of integrations such as #2784.

Meta

In go.mod declare ourself as a tool for our own consumption.

$ go get -tool ./cmd/task

Task developers can now run tasks via 'go tool task'.

This is a first step before further experiments of integrations such
as go-task#2784.
Copy link
Copy Markdown
Contributor

@trulede trulede left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dolmen are you sure this is correct? From what I have read, go get -tool ... would add task as a tool dependency to some project, and you might do it to pin a specific version of a tool.

It seems to not make much sense for a tool to declare itself as a tool.

@trulede
Copy link
Copy Markdown
Contributor

trulede commented May 31, 2026

It was already decided not to do this in the related issue.

@trulede trulede closed this May 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants