So, I just published "Building software together with Git" on my #blog: https://eliotberriot.com/blog/2019/03/05/building-sotfware-together-with-git/ 🎉
It assumes little prior knowlegde from the reader, and attempts to explain the technical concepts in accessible ways.
Merci, vous êtes trop fort·es !
@alice @gordon @maiwann @Lapineige c'est du markdown, qui est visible ici: https://code.eliotberriot.com/eliotberriot/eliotberriot.com/blob/master/_posts/2019/2019-03-05-building-sotfware-together-with-git.markdown
@Lapineige @alice @eliotberriot @maiwann alors, y’a pas de chat sur le pad, mais je suis actuellement dans le train, donc avec une connexion très approximative. Et Sur HackMD, quand on perd la connexion, on ne peut plus taper… Bref, j’espère sincèrement ne pas gêner les choses en écrivant, et je m’excuse pour les périodes où je ne peux pas écrire
@alice @eliotberriot @maiwann @Lapineige j’utilise le plus possible des termes épicènes, puis « masculin ou féminin » (comme « développeuses ou développeurs ») quand ce n’est pas trop lourd, points médians sinon. Mais je pense qu’il faudra de toutes façons harmoniser après rédaction, sur plusieurs points
@eliotberriot Very cool!
Can I ask how you imported the CodiMD text (that's what you used, no?) into your blog?
@kirby sure, since my blog is a Jekyll blog, it supports Markdown format (which is the one used by CodiMD) natively, so it was just a copy/paste :)
@eliotberriot Oh, right, that makes sense 😆
@kirby do you need this yourself for a wordpress blog or someting?
@eliotberriot I was hoping you had some clever, automatic system, maybe even one that supports CodiMDs more advanced features (mermaid, for example) 😅
@kirby ahah, no I don't 😃
@eliotberriot it'd be cool to have this but for non-programmers, having version control on any kind of project can be super useful. there is a video guide somewhere for working with Mercurial for Blender projects, but that's quite long.
Cool analogies! Thanks for sharing 🙂
One comment about "Bob creates the Pull Request". Since you already intro'd branches before, how about building on that to let him send the PR from a `patch` branch. Not master, because this can quickly lead to easily problems for novices. See https://blog.jasonmeridth.com/posts/do-not-issue-pull-requests-from-your-master-branch/ for detailed explanation.
Esp. because it's public & being translated, please consider updating just the branch name. No need to explain it, because that section exactly follows the explanation of branches.
On the contrary: Novices may currently wonder, why you connected the PR example (3rd) back to the section about `master` (1st) instead of continuing the logical flow from before?
@eliotberriot Thank you!
2 little typos: "tyical" & "Gitlab" is technically GitLab ;-)
@gittaca than you, it should be fixed now :)
@eliotberriot Hi, nice take on trying to get more people on board with Git. I made an attempt myself a while ago (but with more of a programmer bent) in case you're curious: http://orangejuiceliberationfront.com/solo-developers-need-source-control/
@uliwitness thank you for sharing. I've found it (slightly) easier to find beginner-friendly resources when you are a dev yourself / or familiar with development, but the more, the merrier :D
@eliotberriot that's a great write up! Hopefully it makes the workflow more accessible. 🙂
One minor nitpick: got doesn't store diff's, it store the full version of each file every time (but only the files that changed)
I'm not sure that matters much though, since the goal is not to be perfectly correct but to vulgarize and make it more accessible.
Again, great work! Thank you!
@mathieu thank you, I didn't knew that, I always assumed Git stored diffs only to optimize storage, but based on that https://stackoverflow.com/questions/10398744/does-git-store-diff-information-in-commit-objects there are also performance implications to store full files with each commit!
I'm sure it's not the only inacurracy/error in the text though, I guess I'm in for a v2 at some point :D
mastodon.eliotberriot.com is one server in the network