Skip to content
This repository was archived by the owner on Apr 21, 2022. It is now read-only.

Add org.label-schema.vcs-branch and org.label-schema.vcs-tag fields to specification#22

Open
lpalgarvio wants to merge 1 commit into
label-schema:gh-pagesfrom
lpalgarvio:patch-2
Open

Add org.label-schema.vcs-branch and org.label-schema.vcs-tag fields to specification#22
lpalgarvio wants to merge 1 commit into
label-schema:gh-pagesfrom
lpalgarvio:patch-2

Conversation

@lpalgarvio

Copy link
Copy Markdown

Two schema additions:

  • org.label-schema.vcs-branch
  • org.label-schema.vcs-tag

Two schema additions:
- org.label-schema.vcs-branch
- org.label-schema.vcs-tag
@lpalgarvio lpalgarvio changed the title Added VCS branch and tag Add VCS branch and tag to specification Mar 6, 2017
@lizrice

lizrice commented Mar 7, 2017

Copy link
Copy Markdown
Contributor

Doesn't vcs URL + ref already uniquely identify the code? My concern would be what if the tag or branch is not consistent with the ref - which is correct?

@stv0g

stv0g commented Oct 28, 2017

Copy link
Copy Markdown

I support having both labels.

@lpalgarvio

Copy link
Copy Markdown
Author

May this get approved and merged?

@lpalgarvio lpalgarvio changed the title Add VCS branch and tag to specification Add org.label-schema.vcs-branch and org.label-schema.vcs-tag fields to specification Nov 15, 2017

@chamilad chamilad left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

These would cover different scenarios that might benefit from clearer lookups for the branch and specific tags.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants