Skip to content

Conversation

@callmeradical
Copy link

Fixes issue #63 tags shows as a branch when issuing

git name-rev --name-only HEAD

On a tagged commit

@CLAassistant
Copy link

CLAassistant commented Nov 4, 2016

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
3 out of 4 committers have signed the CLA.

✅ callmeradical
✅ spiddy
✅ dlozano
❌ Ryan Kennedy


Ryan Kennedy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Member

@dkapanidis dkapanidis left a comment

Choose a reason for hiding this comment

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

It should avoid omitting branches that may include 'tags' inside their name

git.go Outdated

// Branches list is separated by spaces. Let's put it in an array
labels = append(labels, branches...)
if !strings.Contains(branches_str, "tags") {
Copy link
Member

Choose a reason for hiding this comment

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

If I create a branch named "catagsarm" it will be omitted this way because it contains 'tags' inside the text.

What is your current use-case? Does your git spit your tags as branches?

Copy link
Author

Choose a reason for hiding this comment

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

I will have to update this. When listing branches there is a branch named "tags/"

Copy link
Author

Choose a reason for hiding this comment

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

Hey it's updated now, see how that looks?

dkapanidis and others added 7 commits May 10, 2017 22:22
This is quite useful for Continuous Delivery use-cases.

In order for CI systems to propagate the BUILD_NUMBER to captain they can now use '-t BUILD_NUMBER' as parameter.
This will create a docker image with the specific version and push it to registry with 'captain push'
@jwliechty
Copy link
Contributor

This is still an issue when using git 2.17.1. (from a fresh install of Ubuntu 18.04)
Is there a way to move this forward?

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.

5 participants