Remove superfluous go:check template task
#147
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There is an established practice of providing the developer with convenience "umbrella" tasks which collect multiple tasks of a given type of operation. This has a couple of benefits: - Provides an alternative to manually running multiple tasks - Provides a standardized interface to the project, independent from its unique underlying details However, I have come to the conclusion that these benefits lessen as the number of such convenience tasks increases. At the same time, the maintenance burden increases. In the end, my preference is to have only the "umbrella" convenience tasks at the highest possible level, which seems to be: - "build" (build the application) - "check" (check for problems with the project) - "fix" (automatically fix problems with the project) The decision about whether to add mid-level "umbrella" convenience tasks is up to the maintainer of each project, but I don't feel that it's appropriate to provide one as a "template". This task is not used by anything in this repository.
per1234
added
type: enhancement
umbynos
approved these changes
Aug 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is an established practice of providing the developer with convenience "umbrella" tasks which collect multiple
tasks of a given type of operation. This has a couple of benefits:
However, I have come to the conclusion that these benefits lessen as the number of such convenience tasks increases. At
the same time, the maintenance burden increases. In the end, my preference is to have only the "umbrella" convenience
tasks at the highest possible level, which seems to be:
The decision about whether to add mid-level "umbrella" convenience tasks is up to the maintainer of each project, but I
don't feel that it's appropriate to provide one as a "template". This task is not used by anything in this repository.