opencodeiiita / gogit-3.0 Goto Github PK

A project to learn the basics of Git and GitHub.

gogit-3.0's Introduction

GoGit-3.0 🚀🚀

GoGit is a project under OpenCode'23 that aims to improve the Git and GitHub skills of the contributors by completing some tasks. The tasks will be specified in the issue section of this repo and you need to complete these task with all the terms and conditions to be fulfilled. (2 days)

Project Setup 🤝

Don't worry 😅 there is nothing which is needed to be setup. for now, just clone the repo and you are done. You can use any code editor to edit the files (even notepad too).
In the future there will be some files for some tasks that will require builds (Gradle or Maven) but I will be telling you the instruction of the setup at that time only.

Important points ✔️

For contributions, kindly visit the CONTRIBUTING.md file.
I hope untill now you have already take a look at all the issue labels present in this project, if not please visit them.
Kindly visit all the templates present inside the .github directory as they are very very important.
All the basic resources for your understanding are present on the GoGit and git-and-github channel of our discord server.

Communication 🗣️

If you have any doubt, problem or suggestions, you can ping me anytime in the GoGit-3.0 channel of our Discord server.

Guidelines 🔴

Do not make PR which is not related to any issues.
Do not make any irrelevant commits, if you make some by mistakes then please squash them.
Be polite and gentle to other community members.
Pull Request older than 3 days with no response from the contributor shall be marked closed.
Don't worry about the maximum number of commits in a PR, it may vary from issue to issue. (Only valid for this repo) (Also keep the second point in mind)
If somehow I didn't respond to your PR under 40 hours then first try to ping me on GoGit channel and if I didn't reply their too, then you are free to complain about me to the our discord server admins.
Participants who didn't register for the event are not allowed to participate in any repo (project) under opencode organisation.

gogit-3.0's People

Contributors

Stargazers

Watchers

Forkers

satvik7773 sindhu194 aditya4905 apoorv012 aryan4884 criticic thedivineaurora rebornstar1 anshikaswirl ashinat24 vrajshah34 subhranil2004 nandinig24 urvashigoyal803 coderatiiita murdock9803 riya005 aniketh4 believer-99 nishantkale22 ashahmad2022 innocentsinner08 raveenabadavath jeeban-jyoti osamabenlade blackhat-coder21 raj128 vineeshmittal1 nsvpavan yuvrajsingh930 ashutosh9993 adv8j sudhaaaaaydv iam-buddhi divyaagrawal261 nivedh-biju akash-kethavath vasusingla545 aj9630747827 shauryajain03 rnavaneeth992 reene-simon jaysharma100 hannah2k23 piyush-raj-tiwari agatsya0494 mansviii quanttitan komalpardasani abhi5h6k sakshikumar19 gautham-22 apricity24 parth1egend tonystark-jr shayanintekhab rohit-110 lavishmeena2764 vedant2379 ayushk00 meayushsharma saanjh24 prateek2pathak nijval21 aashish-raghav codinjack rishi2674 aryan0931 aayushaeron13 saiushasree1 atharva0192 vidhi1954 legend4137 riri-2k3 dishasoni99 cauxtic illum1nadi arya-007 yashwanth9918 talentedfalcon yogindra3926 rudreshdabre12 shrutikarathi6 shweta-1902 sanjayh-2022 thehackerash tej-as1 shorty-huddybuddy jarviss77 avantika45s rishitha2k4 nilesh9758 anushkp1107 poonamgate tavva-srinivas karansenpai rishikaboinapally deepanshiiiii imsushmitha-13 nitu-sherawat

gogit-3.0's Issues

First time contributors

This issue is mandatory for further tasks as all taks will involve the Info.md file you create in this Issue.

No need to claim this issue

First fork this repo and then clone it to your local system.
Add your info.md file to this repo as I mentioned in the CONTRIBUTING.md
Write something cool about yourself in the "info.md" file.
Now add, commit and push your code and then open a PR.

For any help, Contact us on Go-git and git-and-github channel of our Discord server.

Cherry Pick 🍒

Create a new branch named test-branch and make three commits in the following order: commit-A, commit-B, and commit-C.

Each commit should provide answers to the following questions:

In commit-A, share the name of your favorite fictional character.
In commit-B, let us know about your favorite non-fictional character.
In commit-C, share a quote that inspires you.
Take a screenshot of the git-log of above commits.
After this checkout to main branch
Cherry-pick commit-B into the main branch.
The commit message for the cherry-picked commit should be your "GitHub_username-01".

Make a PR to the main branch, It should include:

The screenshot of the git log.
There should only be a single commit "GitHub_username-01"
No merge conflict

Playing with branches

Create a new branch from the initial commit of this repo and name it "initial-branch".
Then answer the following question in your info.md file.

Ques - You will see that some repo on GitHub has a main branch as their main but some have a master branch as their main branch. So, please explain in which case Git/GitHub creates main as the main branch and in which case it creates master as the main branch.

Now add and commit your answer to this question and create a PR from this initial branch to this repo's dummy-branch.
Condition: You must use the SHA key of the initial commit in any one of the git commands that you will use to complete this task.
PR which will be unable to fulfill the condition can be rejected.
If your info.md file is not there, then you have to make a new one.
No need to claim the issue, First correct PR will be merged.
Make sure to add the commands you used in the PR description.
Failing to do so, Your PR won't be merged

Create Your Portfolio Website

This issue aims to assist beginners in becoming acquainted with GitHub Pages. We invite you to craft a basic portfolio website using HTML and subsequently host it using GitHub Pages.

Create a private repository by yourself
Create a branch "portfolio-website"(necessary) and switch to it.
In that branch, create a new HTML file (e.g., index.html) to build your portfolio.
Details like Name, College, Email, Github profile are a must. You can add many more things..
You can keep it simple or get creative with your design.
Feel free to use any templates online, as this issue only intends to see if you can deploy webpages.
Commit Your Changes
Host Your Portfolio using GitHub Pages
Now add the live link of your hosted page to your info.md file.
Commit changes and make a PR.

Make sure to follow instruction correctly like the branch name. Else PR wont won't be merged.
If you're new to Github, this is a great opportunity to learn!

Include a link to your live portfolio in your PR description as well

Task 2 - Keep Branching 🔀

Task 2

This task consists of the following steps.

Step 1

Checkout to task2 branch.
Create a text file named as github-username.txt. For example, if github username is TheRealSibasishBehera then file name will be TheRealSibasishBehera.txt under CONRIBUTORS/IIITA/SecondYear/SibasishBehera/TheRealSibasishBehera.txt
Write the name of your favourite movie/book in the first line of the file.
Commit this change.

Step 2

Create a new branch feature (and switch to it) from task2 branch.
Write the names of any 2 characters from the movie/book on lines 2 and 3 of the file.
Commit this change.

Step 3

Switch back to the task2 branch.
Write 2-3 sentences on why this movie/book is your favourite, just below its name.
Commit this change.

Final step

Bring the changes from feature branch into the task2 branch.

At the end of this task, you should have exactly 4 commits and the data entered in both step 2 & 3 must be present in the file. Push these changes and make a PR