Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Mathew Foscarini
@thinkingmedia
if you want the true list of branches you need to use the CLI and get the origin branches
anyway I'm just trying to steal you away from pain later on.
Daniel Hough
@basicallydan
I appreciate that, thank you for your input
Mathew Foscarini
@thinkingmedia
you never know if git formats will change in the next year or 2.
but the cli will remain stable
Daniel Hough
@basicallydan
No, you're right. I didn't think it through. Thanks.
Mordechai Zuber
@M-Zuber
What gaurentees that the cli will stay sable though?
Daniel Hough
@basicallydan
It's more likely that the CLI will stay the same than the file structure, I think
Mordechai Zuber
@M-Zuber
devils advocate here
i would hope so
Daniel Hough
@basicallydan
I'm not sure I want to pull down from the branch though
repo*
That seems like something the user should do
Mordechai Zuber
@M-Zuber
OTH if you are using a tool like nodegit - you could assume if the underlying cli changes then the tool will get a major version bump
Daniel Hough
@basicallydan
For nodegit, yeah. I'd hope so!
Mordechai Zuber
@M-Zuber
we are talking about linting a repo from local storage correct?
Daniel Hough
@basicallydan
Correct
Mordechai Zuber
@M-Zuber
you can get tag data without netowqrk calls
tags are a git construct
Daniel Hough
@basicallydan
But are they always kept up to date with every pull?
I'm not going to pull it anyway, so the point is moot :D
Mathew Foscarini
@thinkingmedia
@M-Zuber you can run git --version to check if you support that version and report to the user it's not supported
Mordechai Zuber
@M-Zuber
they should be
Mathew Foscarini
@thinkingmedia
or you can use a nodejs module and defer responsibility to that
Mordechai Zuber
@M-Zuber
there is a --tag flag but I'm not sure what it does
Daniel Hough
@basicallydan
I'm gonna use nodegit, it's decided.
Mordechai Zuber
@M-Zuber
@thinkingmedia it is usually better to blame someone else :)
@basicallydan sorry I told you to delete the code :laughing:
Mathew Foscarini
@thinkingmedia
@M-Zuber and if there is no one to blame you blame God
Mordechai Zuber
@M-Zuber
of some sort
Daniel Hough
@basicallydan
@M-Zuber S'ok, it's still there :) and it'd be in git anyway.
Mordechai Zuber
@M-Zuber
@basicallydan :)
Mathew Foscarini
@thinkingmedia
git ls-remote --heads will list all remote branches without downloading them.
Daniel Hough
@basicallydan
Anyway, the original issue is that I couldn't commit this fake repo. The obvious solution to me is the use nodegit and mock it for the tests.
Mathew Foscarini
@thinkingmedia
^^ yes :)
Daniel Hough
@basicallydan
Cool. I'll get on with that now :+1: thanks chaps :)
Mordechai Zuber
@M-Zuber
Have fun!
Daniel Hough
@basicallydan
Thanks!
Mordechai Zuber
@M-Zuber
Thank you. I hope to gtet back to working on forkability soon. I want to make a prototype for the new rule definition structure.
Daniel Hough
@basicallydan
Yeah! Awesome. :D
Mordechai Zuber
@M-Zuber
(dont remember right now what issue we last spoke about it in)
Daniel Hough
@basicallydan
Nor do I -_-
Oh well!
Mordechai Zuber
@M-Zuber
I'll find it when I start coding
I hope :P
Daniel Hough
@basicallydan
@M-Zuber I realised the day before yesterday that we might've forgotten to do a release.
Or rather, I forgot.
After this: basicallydan/forkability#84
So anyway, I'm gonna do 0.18 now, with #84 and #90
Mordechai Zuber
@M-Zuber
:+1: