bugbash/q4-2022help wantedkind/feature-requestpriority/p2tagger/sha256
Description
The name of the sha256 tagger incorrectly implies that it generates tag based on the a SHA256 digest of the artifact contents. We should
- move the
sha256tagger to the end of the list in docs/content/en/docs/pipeline-stages/taggers.md and document that its use is best used only for CD type jobs - rename the tagger to
latestto avoid any implicit associations, with askaffold.yamlmigration - add a
#sha256-uses-latest-to-tag-imagesref to the doc to explain why it was renamed - rename the
tagger/sha256issue label