‼️ Repositories

Repositories (or repos) are essentially folders where you can store files of code. The repo of our camp was duplicated into your account when you clicked "Create Template" so that you can commit changes and complete each lesson.

‼️ Issues

For our camp, each week is placed inside an issue. Only when you complete the week (committing the necessary code and commenting), will the issue close and you can move on to the next issue. Don’t worry – committing changes is easier than it sounds.

💡 On usual repositories in the contributing world issues are tasks or bugs that need to be completed or fixed.

‼️ Fork

If you want to contribute to someone else's code, you would "fork" it. This creates a copy of the code under your account that you can make changes to. Create a fork when you want to make changes to someone else's code and contribute to it.

‼️ Branch

Creating a branch on a repository is like forking a repository. You would do this when you want to make changes to your code without harming a working version.

‼️ Pull Request

Once you make changes on a forked repository or another branch, you might need to bring the changes into the "main" repository. This allows YOUR changes to be visible in the main project! *You are basically asking for permission to "merge" your changes."

This allows you to:

⭐ Collaborate on code

⭐ Make comments

⭐ Review the contributions made

‼️ Command Line Interface

A Command Line Interface (CLI) is your computer's visual application for accessing its operating system. There are different types of CLIs for different operating systems, such as Terminal for MacOs and PowerShell for Windows. If you have Windows, make sure to also install Git Bash for a better tool. In upcoming issues, we will refer to your CLI as your Terminal or Command Line, but remember that they mean the same thing!

Download VS Code for your operating system and check out this tutorial before getting started.

Inside VS Code, download the following extensions:

• Azure Tools (includes Azure Account, Azure App Service, Azure Functions)
• Live Server

All of the Azure extensions allow you to work on your Azure Function App in VS Code instead of working directly through the Microsoft portal. Live Server is a quick and temporary testing server, and you can use it to test HTML pages. To launch, right click on your html file and press "Open with Live Server" or click "Go Live" in the bottom right corner:

1. Once you have complete the steps in the documentation, clone this repo on your computer
2. Use the following commands to work with branches in the terminal:

• Check which branch you're in: git branch
• Create a new branch and change into it: git checkout --b name-of-branch
• Change branch: git checkout name-of-branch

3. Afterwards, follow this tutorial by VS Code on connecting to GitHub straight from the app!

❗ Make sure you have Node.js and npm installed before moving forwards: https://www.npmjs.com/get-npm

• Check if node is installed: run node -v in your terminal
• Check if npm is installed: run npm -v in your terminal

If you would like to read more, refer to this article on JavaScript and this article on Node.

Example:

function hello() {
    // your code
} 

exports.hello = hello;

When you commit the file, we will try to run the function by importing it and compare it's output to the expected output like so:

let hello = require('../../helloworld.js')
let output = hello.hello()

How does this apply to code in the real world?

Just like you can import code from modules other people have written, you can also import functions you wrote from other files to reuse them. In function oriented programming, you use functions over and over again to save code. If you want to use the function hello() in another file, you would need to import it.

1. Create a new file
2. Name the file helloworld.js
3. Write your code
4. If you have node installed on your computer, open terminal on VS Code and type 'node helloworld.js'
5. If you have not installed node on your computer, you will need to do that first: https://nodejs.org/en/download/
6. Tip: to test your function, call it in your code.
7. Create a new branch named week1 and commit your helloworld.js file in the root directory.
   
   
   

Use the git clone command and replace the url to get your repository's files onto your local computer:

git clone https://github.com/example/example.git

Now is the time to make your changes to your code!

Stage helloworld.js changes only:

git add helloworld.js

Stage ALL your changes to the repository:

git add *

Next, let's commit the code. Usually, your commits will be a group of changes that make sense together. Add a description!

git commit -m "insert your description"

Save your commits to the repository on Github!

git push

For more information, refer to this link