Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

merging a pr #33

Open
tkellen opened this issue Jan 12, 2016 · 3 comments
Open

merging a pr #33

tkellen opened this issue Jan 12, 2016 · 3 comments

Comments

@tkellen
Copy link
Collaborator

tkellen commented Jan 12, 2016

if you delete a branch after merging a pr before hookshot can check it out, the deploy fails.

@cowboy
Copy link

cowboy commented Feb 12, 2016

Is it possible to use the branch's sha instead of its name? I'd imagine the commit would still persist, even if the branch was deleted (I could be wrong)

@brianloveswords
Copy link
Owner

I'd imagine the commit would still persist, even if the branch was deleted

My understanding of branches is that they are movable pointers to commits (opposed to tags, which are static pointers). My test in creating a new branch, making a commit, checking out master and deleting that branch shows that the commit remains:

yep

Interestingly, I only tried for 5 minutes, but I can't figure out how to remove that now-orphaned commit. I tried git gc --aggressive and git remote prune origin (which is a useful command, but not what I was looking for) and neither got rid of it.

@cowboy
Copy link

cowboy commented Feb 12, 2016

It's possible that GitHub aggressively GCs no-longer-referenced blobs, but I dunno. Either way, if hookshot can use the sha of the branch in question, it might be less prone to failure.

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

No branches or pull requests

3 participants