GitHub is a perfect example of my need for some gentle introductory help.
I assume that the GiHub site has some helpful information but it would be most excellent to have something here that provides some tips for getting a start on navigating GitHub.
Can you recall what was confusing about github or what you were trying to do? If you’re not coding, usually you can go to a ‘repo’ or repository (which is pretty much a folder) and download that folder.
Again, a little more substance on what you’re trying to achieve would help in terms of providing or pointing you at better docs. So for example, which of the following are of interest?
Getting the latest version of a particular script
Keeping track of your own revisions to that script
Contributing your changes back to the original author
There are a ton of tutorials for git out there, of various levels of quality/user-friendliness. Without knowing what you’re trying to do, it’s harder to point you in the right direction.
My issue is basically that I’m not even sure what I want to do yet! So what would be helpful to me is a “for dummies” primmer kind of introduction, enough to give an indication of what is even possible…
Maybe a couple good general github tutorial links would be helpful. I think I’m navigating it okay, but there are a lot of words like ‘blob’ and ‘commit’ that can be confusing.
@dan_derks I think this is a great start, thanks for doing it! Would be nice to know what norns programs support Crow, like maybe a running list. Would save digging through the library to sort it out. I’m sure I will have many more questions upon delivery and installation but I’m confident this awesome community will point me in the right direction, as they always do.
Of course I already have a question: Why 3.33 volts? I’m not asking that expecting you to explain it there, but maybe a link to why that matters would be helpful.
Second immediate question is how can we learn about the syntax Crow is expecting?
There may be more questions but that is what initially hit me…
Sincerely not trying to be critical or annoying here, just sharing the “in the moment” thought process as I’m experiencing it…
Tutorial on this for noobs would be great. I’ve tried to figure out what all this “git pull request” business is all about to no avail. As of now I manually download and replace any script I want to update via Cyberduck:man_shrugging:
OK, let me see what time I can find to do this. Likely to be a rambling tour, but hopefully enough to get you started. BTW, a “pull request” is a way of asking the owner of a repository to merge some changes that you’ve made, but I’ll go through that in detail in the video.
I will say that I’m an old school command line guy, so will be using the command line git tools. There are some nice, much friendlier GUI tools available, but that’s not really my thing, and I think it’s worth learning the underlying tools.
@dan_derks there was a comment (which I now can’t find) made about the pullups about not enabling this on Crow if it was also done elsewhere (TT i2c bus board?) . Can you add some commentary about this, and what happens if you do? Does it simply cause issues in data transmission over i2c? Or something worse?
Edit to add: sorry, I see there is a comment about only one needing to be enabled, but nothing to say what happens if you mistakenly enable a second.