GitHub: Branches, Issues and First CRUD

Next, we move on creating a first CRUD of Links.

This is the final visual result, after this lesson:

It will be a simple list/create/edit/delete feature, so not that much to talk about from code perspectice. As with everything in this course, let's focus on processes: the important part is that we will set up GitHub and branches.

Let's configure and prepare all on GitHub BEFORE writing any new code.

1. Create an empty GitHub repository
2. Follow its instructions to push the code so far

git init
git add .
git commit -m "Initial Laravel Breeze and DB Models"
git branch -M main
git remote add origin https://github.com/[your_name]/[your_repo].git
git push -u origin main

The default first branch is called main (unless you changed it to something else, but I will go with the defaults).

And now the question is whether we should continue working with that branch, or create a separate one.

In this course, we assume you're working in a team of at least two people, so you do need to collaborate on multiple features at once, before pushing them to live.

With that in mind...