#64

Forks vs branches, well in this context, the way that @okyeron has described it is fair enough. A fork can also be thought of as a server-side clone. These things get a little more complex when you have a team of developers collaborating on adding sets of features to the same codebase, each of whom has access to push changes to the same repository. That’s usually where branches make sense, but that’s really beyond the scope of what we need here.

2 Likes
#65

I just found out that not every repository has an issues tab. That might had confused me.

#66

We use the “GitFlow” model where I work. I use a variant in my own projects as well, minus forking. Like, I don’t fork my own project and then create PR’s against it.

At any rate, the reason I mention Gitflow is because this explanation of the method might be a helpful illustration of how branching and forking works, or can work.

2 Likes
#67

Just wanted to say that I’ve not forgotten about this thread, and I do plan to take another pass at creating a git intro video (possibly also using the GUI tools). It’s just things have been more than a little busy.

2 Likes
#68

This is probably not the most coherent demo, but I recorded a quick session while sharing the Karplus-rings version of awake this morning:

1 Like
#69

@burns_audio I’m writing my reply here, since it’s not something Scrum/Agile specific:

Git Large File Storage might be interesting for you. Here’s a short article about using it for versioning Ableton Live projects.

That being said, I’ve been storing some pretty large files in my private Bitbucket/GitLab repositories, while playing around with some music related machine learning stuff. Worked fine, even without LFS.

1 Like
#71

All well-covered here already, but wanted to link for posterity an annotated shell session of a typical workflow for something like modifying Teletype firmware.

1 Like
#72

I wrote up a very simplified tutorial of sorts for absolute beginners called Git for Misfits (and artists) here

My goals were:

  • explain basic use case for git/github in simplest terms possible
  • some (visual and conceptual) artist and museum examples
  • how to create and work with a project repo on github in the browser (easiest)
  • basic git workflow (intermediate)
  • abusing autocomitting to simplify the commit process for non collaborative repos (for misfits)

Hopefully it’s useful for some folks, and I’m open to any questions or feedback

1 Like