An open API service indexing awesome lists of open source software.

https://github.com/tafara-n/alx-pre_course

I'm now a ALX Student, this is my second repository as a full-stack engineer.
https://github.com/tafara-n/alx-pre_course

documentation emacs git github linux right-engineering-right-documenting vi

Last synced: 7 months ago
JSON representation

I'm now a ALX Student, this is my second repository as a full-stack engineer.

Awesome Lists containing this project

README

          

# Concepts

*For this project, we expect you to look at these concepts:*

- [Struggling with the sandbox? Try this: Using Docker & WSL on your local host](https://intranet.alxswe.com/concepts/100039)
- [Authenticating Git](https://intranet.alxswe.com/concepts/100035)
- [Source code management](https://intranet.alxswe.com/concepts/22)
- [Right-engineering, right-documenting](https://intranet.alxswe.com/concepts/6)
- [Git and Github cheat sheet - Everything in less than 30 seconds](https://intranet.alxswe.com/concepts/57)

# Resources

## Read or watch:
- [Resources to learn Git](https://docs.github.com/en/get-started/getting-started-with-git/set-up-git)
- [About READMEs](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)
- [How to write a Git commit message](https://cbea.ms/git-commit/)

# Resources for advanced tasks (**Read only after finishing the mandatory tasks**)
- [Learning branching](https://learngitbranching.js.org/)
- [Effective pull requests and other good practices for teams using GitHub](https://codeinthehole.com/tips/pull-requests-and-other-good-practices-for-teams-using-github/)

# Learning Objectives
At the end of this project, you are expected to be able to [explain to anyone](https://fs.blog/feynman-technique/), **without the help of Google:**

## General
- What is source code management
- What is Git
- What is GitHub
- What is the difference between Git and GitHub
- How to create a repository
- What is a README
- How to write good READMEs
- How to commit
- How to write helpful commit messages
- How to push code
- How to pull updates
- How to create a branch
- How to merge branches
- How to work as collaborators on a project
- Which files should and which files should not appear in your repo

# Requirements

## General
- A `README.md` file at the root of the `alx-zero_day` repo, containing a description of the repository
- A `README.md` file, at the root of the folder of this project (i.e. `0x03-git`), describing what this project is about
- **Do not use GitHub’s web UI**, but the command line to perform the exercise (except for operations that can not possibly be done any other way than through the web UI). You won’t be able to perform many of the task requirements on the web UI, and you should start getting used to the command line for simple tasks because many complex tasks can only be done via the command line.
- Your answer files should only contain the command, and nothing else

# More Info

## Basic usage
At the end of this project you should be able to reproduce and understand these command lines:

```shell
$ git clone
$ touch test
$ git add test
$ git commit -m "Initial commit"
$ git push origin main
```