#git tutorial

[petrapixel]

here's a list of all the intermediate coding tutorials i've written so far!

git / github tutorial

npm (and node.js) tutorial (+ how to use the command line) (this one's a prerequisite for the following 2 tutorials)

webpack tutorial (a module builder for JavaScript and (S)CSS)

11ty (eleventy) tutorial (a super easy static site generator!)

if you have ideas/requests, feel free to contact me!

more beginner coding tutorials are coming VERY soon! meanwhile, check out my common questions and common mistakes pages!

[thecommoncoder]

Git Tutorial: Learn How To Use Git in 23 Minutes!

Do you want to learn how to use Git? In this tutorial, we'll cover the essential Git commands that you need to know, so that you can start using version control inside of your projects. Enjoy! 🎉 #git #gittutorial #howtousegit #thecommoncoder

[badolmen]

Actually it really fucking frustrates me as a disabled person how ‘controversial’ video game accessibility is, how contrived it is to find actually useful accessibility mods for even popular games, how abled gamers try to distance themselves from us because we’re the ones without social lives, who don’t leave the house, who can’t work.

[townofcrosshollow]

Using Git for Twine Games

A while back, I somehow managed to copy the contents of one file and overwrite a different file, meaning the entire section of the map was lost for good. I had to reconstruct it from snippets of prose written in separate documents. It sucked. And that motivated me to try something that would stop that problem from ever happening- hosting my project on GitHub!

Git sounds really fancy and hard to understand, but it's really not! So I'm going to walk you through how to use it to back up your files and do much, much more.

This tutorial expects you to have an already set up Tweego folder and VSCode. If you don't know how to get that started, @manonamora-if has an excellent ready-to-use folder with an explanation of how to use it.

What is Git?

In short, git is a kind of version control. Say you're working on a coding project with somebody else, and you need to work on the same file they were working on. But how do you know you're working on the right version of that file? Maybe they forgot to send you the newest version. Or maybe you both have to make changes at the same time. It would take a lot of effort to manually splice together everybody's changes, let alone identify what each of you had changed. That's what git's job is. Git identifies what has changed about a file, notes those changes, and updates the "main" files to match. That way, everything stays consistent, and big files can be updated easily.

Okay, but what benefit does git provide to you, somebody who's just working on a solo project with very little code? Well for one, it would have completely fixed my problem. Instead of overwriting all of my work, git would have shown me that the file had been changed. Then, I could simply click a button to revert the change. Neat! It also means you can keep working on the same project from multiple locations without losing progress. Say you're working on your game on your home computer, but then you want to keep working on your school laptop. All you'd have to do is "push" your changes to save them to your master file, and then "pull" the changes when you get to school. Neat

The Basics of Git

Okay, but what does "push" and "pull" mean? Git's confusing, but the basic terms you'll be encountering don't have to be! Here's some terminology:

Git - This is the program that goes on your computer to manage your files. It does all of the version control.

GitHub/GitLab/BitBucket - These provide servers you can host your git repositories on.

Repositories - This is a fancy word for a folder that's being maintained by git. Every file in a repository is getting analyzed by git for changes.

Local vs Remote - Your local repository is the one hosted on your computer, and it's the one you're editing. The remote one is the one hosted on a site like GitHub.

Stage - When you stage a file, you're getting it ready to commit it.

Commit - A commit is like saving your progress as a new update. You can go back to a commit later if you messed something up.

Push - When you "push" your commits, git will look at your changes, go into the remote repository, and individually change all of those things in the "main" branch.

Pull - Just like pushing, when you pull, you're taking changes from the remote repository and updating your local one to match it.

Under the cut, I'll show you full step-by-step (with photos!) of how to set up your game with GitHub using VSCode!

Setting Up Git With VSCode

Lucky for you, VSCode has built in integration with GitHub, which means you don't have to download any new programs other than git itself. You'll just have to set it up. A note- I'm not sure at what point exactly in this process VSCode prompts you to install git, because I'm not going to install it on another computer just for this tutorial haha. VSCode will provide the installation, just go along with the default settings and you'll be fine.

So first, make a Github account. It's free!

Now, open VSCode. Here's our project! You're going to want to click on that third button down in the side menu, the Source Control tab.

Under source control, you'll see this option. Click it.

Aaaaand it's done! That was easy, right? Now your folder is a git repository. Crazy!

Before you can put all of this up in GitHub, you'll need to push all of your files. Type a brief message (try "Initializing" to feel like a real cool coder), press commit, and VSCode will ask if you want to skip staging and just commit everything. Yes! Yes you do!

Now that all of your "changes" have been committed, let's publish your new repository to GitHub. Click on the new button that says "publish branch." When the popup appears, click "Allow" to give VSCode access to your GitHub account and sign in. Back in VSCode, you'll see this:

You're probably going to want it to be private, otherwise anyone on the internet could see all of your writing! Which is cool if it's a public coding project that people might want to download and use for their own projects, but if you're not a fan of code diving, leave it private.

Using Git To Help You Write

Now that you've got your folder set up as a git repository, it'll change the way VSCode looks. VSCode is using git's info to know where you've made changes, and it'll represent those changes in the UI. Here's what those look like:

If you click on those lines, you'll get to see this fancy new panel that highlights all of your changes:

So let's say we have a scene, and we aren't happy with how it's looking, but we aren't sure if we want to make one change or a different change. Instead of backing up all of your stuff or copy and pasting it to test it, you can just make whatever change you want and click that backwards facing arrow to revert it back if you aren't happy with it. You can do the same for things like CSS- when you've made some good progress and want to save your changes, commit them. Then any more changes you make will be easy to revert back if they don't look right. Groovy!

Now that everything's set up, it's as easy as committing your changes when you're satisfied with them and pushing those commits to back up your work.

Pat yourself on the back! You just learned (the very basics of) how to use git! You absolute genius!

If you have any questions while following this tutorial, feel free to ask! My askbox is always open!

[starcell00]

(warning: this post is mostly about silly little video games, but it mentions traumatic methods of teaching and their results. also, minor early-game spoilers for Outer Wilds.)

Outer Wilds and the Dark Souls series approach the problem of what to do when new players fail at the game from opposite directions, and (at the risk of pissing off soulslike enjoyers) I think Outer Wilds does it right, and Dark Souls does it wrong.

When a player dies in Dark Souls, the screen briefly flashes with the iconic "YOU DIED" before fading to black and putting them back at their most recent campfire. At first glance, this doesn't seem like anything more than the game telling the player the obvious, but...

"YOU DIED". There's so much emotional content packed into those two words.

The player already knows they've died when they see their character take the final hit and crumple to the ground dramatically, before those words ever hit the screen. Iconic though it is, the phrase is unnecessary; but it's also worded in such a way that it aims itself squarely through the fourth wall at the player themself. When you see it for the fiftieth or hundredth time, it starts to read as a judgment from the game, and the deaths start to feel like personal failings.

Coupled with the notorious, punishing difficulty of the game itself, Dark Souls' method of developing skill in the player boils down to "repeatedly demanding competency, until the player develops the ability to give it." If they develop that ability quickly, or by being persistent enough, they're rewarded with a slow trickle of lore and worldbuilding as rich and deep as amber - which is something that Dark Souls shares with Outer Wilds.

But if they fail to develop this ability in a timely manner, or even at all, a particular boss or area can quickly become a brick wall for the player to hit their head against. In this way, the game's teaching style is roughly analogous to a strict piano player rapping their student across the knuckles and saying "Again" every time they hit a wrong note; this harshness and lack of sympathy from the game is even a meme in the Dark Souls community, with many a comments section littered with "git gud."

(tw: this is where it gets heavy)

Although Western society has largely moved on from corporal punishment, this "just get good" style of teaching is still regularly practiced in almost all areas of real life, and - speaking from personal experience - the consequences for students are usually severe: from loss of passion for the material, to lifelong insecurities and anxiety disorders, to crippling depressive tendencies, up to and including suicide. The entirety of Whiplash (2014) comes to mind, but particularly the bit where the harsh band director gets physically attacked by his star drum student.

(ok ur good)

By contrast, Outer Wilds takes great care to frame the player's death as a natural inevitability. You can glean every bit of information from every NPC in your starting village and go take off in your wooden shack of a spaceship, you can land (very gingerly) on your home planet's moon and talk to the NPC hanging out there, you can take off again, land again at the places on the moon they suggested you go to, and translate some alien text, you can go to some more places, and rinse and repeat for twenty minutes...

...and then, you can look skyward and watch the fucking sun explode, turning you and every other bit of matter in the solar system into a glittering cloud of plasma.

The game unequivocally tells you, within the first half-hour of gameplay: "you will die, and that's okay." In fact, it proactively makes you die, at no fault of your own - without even saying any words about it, to boot. (Interestingly, this can sometimes be a major turn-off for soulslike enjoyers.)

You then wake up back where you started, and your ship's computer still has logs of the people you talked to and the text you translated in the previous life, ready for you to take off again and add to them. Outer Wilds defines success such that you only fail if you manage not to learn anything in a life - an exceptionally difficult thing to do, given how plentiful knowledge is in the worlds you visit.

In fairness, though, Outer Wilds does have areas locked behind requirements of lateral thinking, unusual cunning, or raw mechanical skill, and you will not be progressing into those areas until you meet those requirements. The game temporarily switches to the Dark Souls model of teaching: demanding competency until you develop it. Given some of the places it shows up, the switch usually makes sense, and the areas in question are still largely optional (let's not talk about the DLC), but it says something about that model of teaching that those moments are widely considered to be the worst parts of the game.

tl;dr Dark Souls demands perseverance and punishes failure, where Outer Wilds encourages perseverance and makes true failure quite difficult. Some people want Harder Battles, but some people can't handle them.

[snowy-nostalgia]

Hey, if you can shade/render blue, green, purple, etc, you can shade/render shades of brown. Stop whitewashing Amanda JFC ITS NOT HARD. The amount of people ive seen on tiktok whitewash her is painful, i mean it shouldnt be happening at all but the sheer amount is unbelievable

[ibarrau]

[Fabric] Integrar repo GitHub con área de trabajo

Una característica que no para de causar revuelo y preguntas al momento de persistir los desarrollos de Fabric es la integración de áreas de trabajo con Github. Desde el lanzamiento de Fabric podíamos integrarnos a un repositorio, pero era exclusivamente con Azure DevOps. La historia continuó con el lanzamiento de Power Bi Projects que nos permitía desagregar el desarrollo de un pbix en código para poder persistirlo y mergearlo. La cuenta pendiente más grande de desarrollos de Power Bi estaba saldada. El desarrollo ya podía ser versionado en su totalidad.

En este artículo vamos a ver como configurar un repo de Github para estar integrado con un Area de trabajo en Fabric/PowerBi.

Lo primero que recomiendo si están iniciando este artículo sin conocer que es una integración de Git en un área de trabajo es pasar por este artículo anterior que explica el funcionamiento y la desagregación de archivos que consolidan un Proyecto de Power Bi.

Prerrequisitos

Cuenta de Github

Repositorio creado (se recomienda privado para desarrollos y manejo de datos corporativos sensibles)

Una Personal Access Token (PAT)

Un área de trabajo con capacidad dedicada

Asumiendo que conocemos como crear una cuenta de Github y un repositorio, comencemos con la creación de la PAT. Para ellos vamos a nuestro perfil, menú settings > Developer settings. Los tokens de acceso pueden ser classic o fine-grained. Recomiendo crear fine-grained que son la próxima generación de tokens y es bueno estar actualizados.

https://github.com/settings/tokens?type=beta

Delimitamos un nombre para nuestro token de acceso y en el apartado de permisos seleccionamos Read and Write para Contents.

Tras crear el token es necesario guardar el valor generado porque no podremos volver a verlo. Copienlo bien y resguárdenlo.

Ahora si podemos volver a PowerBi para abrir las configuraciones del área de trabajo en la parte de integraciones de Git. Hay dos configuraciones. Iniciamos logueando el proveedor con la dirección del repo y el token:

Una vez configurado se ve así. Continuamos sincronizando el pertinente Branch que nos permite seleccionar inclusive una carpeta o subcarpeta especifica. Tengamos presente que símbolos y espacios en las carpetas podrían generar dificultades para reconocerlas.

Así conseguimos nuestra integración para comenzar a trabajar en equipo sobre los reportes y modelos semánticos desarrollados como Power Bi Projects o elementos de Fabric.

Esta sencilla configuración nos permite comenzar a versionar nuestros desarrollos de PowerBi con simplemente una capacidad dedicada puesto que Github cuenta con servicio gratuito que fortalece no incorporar una licencia adicional.

Otros repositorios

Las áreas de trabajo permiten integración con dos repositorios Git hasta el momento (19-09-2024), Azure DevOps y GitHub. veamos algunas comparaciones entre las plataformas:

Si queres saber más sobre la integración con Azure DevOps podes ver este post.

Así completamos nuestro artículo para conectar un repositorio GitHub con un Área de trabajo. ¿Cual usar? depende de cada organización respecto de que tecnología se adaptaría mejor o cual están usando actualmente.

[thedimensionxyz]

#00248

If you've ever come across a GitHub project site and wondered what it was all about (or just how to download the project), then this course by Stephen Ulibarri is a great short course.

My plan is to use both GitHub and Perforce as follows:

GitHub: for building Unreal Engine from source and testing out C++ code

Perforce (Helix Core): for Unreal Engine projects and its assets (eg. Houdini files)

[space--continuum]

Git explained like video games! 🎮

art.png art2.png art-final.png dkfjsdfjioksd.png 😭😭😭

Does this look familiar? Let me show you an awesome tool called GitHub Desktop

[bumblebeerror]

Minecraft hardcore tips that are not “git gud”

Aka these won’t save you from everything but it’ll prevent a lot of deaths. You do not have to be an excellent pve’er to survive in hardcore it just helps a lot

The first priority is food, followed by a bed. The more mobs you can prevent from spawning, the better. Your base is now the first place you manage to make a house in before night falls - plains are good for this but don’t go looking for one until day.

TAKE YOUR BED/A BED WITH YOU WHEN YOU LEAVE BASE FOR EXTENDED PERIODS OF TIME. Skipping night usually means nothing can spawn as long as you sleep immediately.

Next is torches. You can use logs to make charcoal, and charcoal can be used to make them. Torch spam your entire area, so that you can’t see any unlit areas from your base. This will prevent spawns nearby, which gives you an almost forcefeild against mobs - if you’re a couple chunks (16x16 blocks) from the nearest mob it won’t pathfind to you. And the fewer mobs spawn, the less chance of a hoard.

Don’t set up near rivers or oceans unless you’re good with a shield. Tridents can kill you in enchanted netherite in about 6 hits.

If you are not good with a shield, that’s fine. Prioritize armour. You can find diamonds when stripmining still - they’re at bedrock level. Keep your tunnels lit. If you want netherite it’s frankly safest if you have fire resistance, but you can get by with food and a set of blast and fire prot armour. Don’t make it from diamonds unless you’re farming villager trades.

A water bucket is extremely helpful, and so is just. Placing water under yourself. Effective shield against mobs touching you. Likewise, endermen will not teleport into water - if you need time to regen health, place water or jump into a pond or lake.

Redstone and making farms for items is EXTREMELY helpful. Tutorials are pretty easy to find for just about everything you could want to farm, too. Some are more labor intensive than others.

Feel free to reblog with the things you do too :] Minecraft doesn’t have to be a git gud game.

[max1461]

Can someone explain to me in like five seconds how to use git, assuming that I know basic shit about coding/command line/whatever but don't know any of the specific terminology related to git. Like every tutorial online is at the same time both over my head and also vastly too basic. Just like. Tell me what it is.

Uh. First tell me its ontology. Is it a program, a standard, a language...? I know that it's for version control. Suppose I wanted to do version control at a piece of code. What do I do. What buttons do I press, on my computer? Tell me these things.

[frog707]

Where was this back when I was learning Git??

FINALLY got done with the Beginners guide to GIT

So a long time ago I made a poll to help me make a Begginers guide to GIT because a lot of people seem to have trouble with it. https://www.tumblr.com/moose-mousse/722172571753365504/going-to-make-a-getting-started-with-git-post?source=share

And I know for a fact that my University taught it horribly. (Or rather... did not teach it at all)

I REALLY tried making this guide as short as I possibly could. Explaining only what you need to know, while trying to clarify what most people find confusing. But it still is too long for a single post. So, I have split it into 5. The post each links to each other, so you should be able to go back and forth easily.

This guide is going to be pure GIT done via the command line. 2 reasons for this:

1: GIT GUI’s are really handy, but they abstracts away a lot of the newbie help GIT is trying to give you. Bitbucket, Github, Jira, and other services use GIT but usually add extra bits that are specific to them. So to know how they are different, it is smartest to learn pure GIT first. And since they are 99% GIT, you will be able to use them with no/little trouble.

2: Because I use the command line, it is easy to build your own automation tools. Simply have a program write git commands to the shell and/or read outputs from git commands and use them to visualize whatever you want, however you want. That way you can have whatever shiney graphics your heart can code up. All the tools you can find (Like Github desktop or gitk) are simply doing this. (incidentally, if any of you make a pretty visualization of GIT? Show me! I wanna see a dog themed GIT graph! I wanna see pink log outputs! Make it yours!)

Table of content: Part 1: What is GIT? Why should I care?

Part 2: Definitions of terms and concepts

Part 3: How to learn GIT after (or instead of ) this guide.

Part 4: How to use GIT as 1 person

Part 5: How to use GIT as a group.

[ibarrau]

[PowerBi] Integración con AzureDevOps Git Repos

El lanzamiento de Power Bi Developer Mode durante el evento Microsoft Build está causando gran revuelo no solo por su posibilidad resguardar un proyecto de PowerBi sino también porque por primera vez tendríamos la posibilidad de que dos o más usuarios trabajen en un mismo proyecto. Esto no es trabajo concurrente instantáneo como Word Online sino más bien cada quien modificando los mismos archivos de un repositorio y logrando integrarlos al final del día.

La deuda de versionado y trabajo en equipo finalmente estaría cumplida. Según uno de los personajes más importantes del equipo, Rui Romano, aún hay mucho por hacer. Veamos que nos depara esta característica por el momento. 

Vamos a iniciar asumiendo que el lector tiene un conocimiento básico de repositorios. Entienden que en un repositorio se almacenan versiones de archivos. Se pueden crear ramas/branches por persona que permita modificar archivos y luego se puedan integrar/merge para dejar una versión completa y definitiva.

Todo esto es posible gracias a la nueva característica de Power Bi Desktop que nos permite guardar como proyecto. Esto dividirá nuestro pbix en dos carpetas y un archivo:

Carpeta de <nombre del archivo>.Dataset: Una colección de archivos y carpetas que representan un conjunto de datos de Power BI. Contiene algunos de los archivos más importantes en los que es probable que trabajes, como model.bim.

Carpeta de <nombre del archivo>.Report: Una colección de archivos y carpetas que representan un informe de Power BI. El archivo más importante es "report.json", aunque durante la vista previa no se admiten modificaciones externas en este archivo.

Archivo <nombre del archivo>.pbip: El archivo PBIP contiene un enlace a una carpeta de informe. Al abrir un archivo PBIP, se abre el informe en  Power Bi Desktop y el modelo correspondiente.

Entorno

Lo primero es configurar y determinar nuestro entorno para poder vincular las herramientas. Necesitamos una cuenta en Azure DevOps y un workspace con capacidad en Power Bi Service. Para que la integración sea permitida necesitamos asegurarnos que nuestra capacidad y la de la Organización de Azure DevOps estén en la misma región. 

La región de una organización de Azure DevOps puede ser elegida al crearla, al igual que podemos elegir la región de una capacidad cuando creamos una premium, embedded o fabric.

En caso de utilizar capacidad PowerBi Premium Per User o Fabric Trial, no podríamos elegir la región. Sin embargo, podríamos revisar la región de nuestro PowerBi para elegir la misma en Azure DevOps

En ese caso creamos la organización de DevOps igual que nuestro PowerBi porque haremos el ejemplo con un workspace PPU.

Seteo

Dentro de Power Bi Service y el Área de trabajo con capacidad que queremos versionar iremos a la configuración. Con la misma cuenta de ambos entornos completaremos los valores de organización, proyecto, repositorio, rama y carpeta (opcional).

Como nuestro repositorio esta vacío, lo primero que sucederá cuando conectemos será una sincronización de todos los items del área de trabajo en el repositorio. Ahora bien, si teníamos reportes en el repositorio y en el area,  tendremos un paso más para coordinar la operación deseada si pisar o integrar.

Una vez que todo tenga tilde verde y esté sincronizado, podremos ver como queda el repositorio.

En caso que ya tuvieramos informes cuando inicio el proceso, se crearán carpetas pero no el archivo .pbip que nos permitiría abrirlo con Power Bi Desktop.

Si crearamos el informe con Power Bi Desktop y eligieramos “Guardar como proyecto” si se crearía. Entonces podríamos hacer un commit al repositorio y automáticamente se publicaría en nuestra área de trabajo.

El archivo pbip es un archivo de texto. Podemos abrirlo con un bloc de notas para conocer como se constituye para generarlo en caso que necesitemos abrir con Desktop uno de los informes que sincronizamos antes. Ejemplo del archivo:

Al tener sincronizado el repositorio con el workspace podemos usar un entorno local. Si está en el repositorio en la rama principal, entonces estará publicado en el área de trabajo. Veamos como sería el proceso.

Esta sincronización también nos favorece en el proceso de Integración y Deploy continuo puesto que varios desarrolladores podrían tener una rama modificada y al integrarlo con la principal delimitada en el área de trabajo tendríamos automáticamente todo deployado.

Si algo no se encuentra en su última versión o hacemos modificaciones en línea, podemos acceder al menú de source control que nos ayudaría a mantener ordenadas las versiones.

Alternativa Pro

Con las nuevas actualizaciones de Fabric en agosto 2023, podremos por primera vez, trabajar en equipo en PowerBi sin licencia por capacidad o premium. Guardar como proyecto es una característica de PowerBi Desktop. Por lo tanto, podemos usarla contra un repositorio Git en cualquier tecnología. Al termino del desarrollo, una persona encargada debería abrir el PBIP y publicarlo al área pertinente. Ahora podemos publicar desde Desktop los informes guardados como proyectos. Esto nos permite que los casos de puras licencias pro puedan aprovechar las características de histórico y control de versiones. Quedará pendiente la automatización para deploy e integración que aún no podría resolverse solo con PRO.

Conclusión

Esta nueva característica nos trae una práctica indispensable para el desarrollo. Algo que era necesario hace tiempo. Sería muy prudente usarlo aún en proyectos que no modifiquen un informe al mismo tiempo puesto que ganamos una gran capacidad en lo que refiere a control de versiones.

Si no tenemos capacidad dedicada, deberíamos trabajar como vimos en post anteriores sobre metodología de integración continua de repositorio https://blog.ladataweb.com.ar/post/717491367944781824/simplepbicd-auto-deploy-informes-de-powerbi

Esperemos que pronto tengamos una opción para importar por API estos proyectos al PowerBi Service para poder idear nuestros propios procesos sin usar las integraciones por defecto sino una personalizada a nuestro gusto.

[markrosewater]

hi a friend walked me through a commander game and I liked it and so I got a couple premade decks. I then went to a couple commander nights and I kinda liked it except for the part where I felt like I was a little kid with floaties in the middle of the ocean trying to sing a little song to myself so I wouldn't think about the things that might be lurking just below the surface that I can't see. Magic is vast and deep and I don't know how I can enjoy playing when there's just too much. I get that the hugeness is part of its staying power, but it feels too big and too much to even approach beyond playing my premade deck and hoping the people at the table won't look down on me for it (which they often do). Even looking up tutorials and guides is overwhelming because each one of them is sharing a *different* tiny slice of material! I haven't felt this baby-beginner starting something new in a very long time (and I say that as someone that is otherwise well-versed in being a terrible beginner at new things). Is there a way to play magic without getting absolutely lost in the depths? or is that the nature of the beast and I just gotta "git gud"?

The two formats I would suggest are draft or Cube. Both use a much smaller card pool, one you can more easily learn about.