challenge 1 -30 (0xPratyush)

[0xPratyush]

name: Pratyush Panda github_user_name: 0xPratyush

[0xPratyush]

• URL : https://github.com/0xPratyush/scaler-september-open-source-challenge

[0xPratyush]

Screenshot showing the required branch inside forked clone repository :

[0xPratyush]

Updated forked repository locally with the content of the original repository for both the main branch and the branch that I created in Challenge 3 using the git remote add upstream command

Screenshots attached below.

Updated in main

Updated in branch i created

[0xPratyush]

Challenge 9 done 👍

(forgot to add a commit message inbetween :( )

[0xPratyush]

Done with day 10 challenge

[0xPratyush]

**Challenge 11

creating a new branch**

[0xPratyush]

Challenge 13 :-Use the git stash command to move these changes to the stash area

[0xPratyush]

Day 14 Challenge

[0xPratyush]

Challenge 15 done

[0xPratyush]

Challenge 16 done

[0xPratyush]

Challenge 17

• Created the repo and published

• Created a new branch

• Edited the README.md file in main branch

• Pushed the commits with the updated README.md file

[0xPratyush]

Challenge 20

• Link to repo
• Link to Project

Screenshot attached below**

• Todo

• In Progress

• Done

[0xPratyush]

Challenge 21

Created 2 alias for any git commands and shown their usecase

Take a screenshot of the alias you created. hint run git config --list

[0xPratyush]

Challenge 22

• Create a new repository on GitHub
• Create a basic static website about yourself
• Add your html site to your respository.

• Host your site on GitHub pages
• Screenshot of page

[kuraakhilesh8230]

1.too many commits 2.not done challenge-20 correctly because each and every ss should be attached and lastly all the files should be in done with tick mark complete this by sunday to avoid rejection

[0xPratyush]

Here are the summary which I learnt from today's task. (Day 23 task)

Git branches are of two types:

1. Regular
2. Temporary Branches

Regular Branches

• These branches will be available in your repository on permanent bases.
• Their naming convention is simple and straightforward.

Temporary Git Branches

As the name indicates, these are the branches that can be created and deleted when needed. They can be as follows:

• Bug Fix
• Hot Fix
• Feature Branches
• Experimental Branches
• WIP branches

Git Branching Naming Convention

• Start branch name with a Group word like Bug – The bug which needs to be fixed soon
• Use Unique ID in branch names like wip-8712-add-testing-module
• Use Hyphen or Slash as Separators like feature_upgrade_jquery_version_login_module
• Avoid using numbers only like 9912
• Avoid using all naming convention simultaneously
• Avoid long descriptive names for long-lived branches like wip_login_module_which_will_used_in_the_public_website

Building a Great Pull Request

• Give your feature branch a clear name
• Give your commits and PRs active and descriptive titles
• Streamline your process of creating a new PR
• Give your PR a meaningful description
• Show your functionality visually, whenever possible

Contributing Guidelines

• Always see for good-first-issue in the repos.
• Comment on it and say you're working on that issue, to avoid conflicts with others while also working on the issue.
• If you want to make changes which are not specified in any issue, or you find any bug, first create a new issue and then wait until it is assigned to you.
• Have a clear purpose while creating a new issue.
• Avoid long descriptive names

[0xPratyush]

Day 24

• First of all done some research regarding some projects,watched some youtube videos regarding open source and how can i get more out of it. then i got my first issue assigned.

[0xPratyush]

Day 25

• Contributed on the issue assigned
• pull request approved and merged

For repository link:- click here For issue link :- click here

Now search for the next possible contribution beginsss . . . .

[0xPratyush]

Day 26

• Registered at Hacktoberfest 2022

• Collaberated with some folks in the discord community regarding the preparation for hactober fest how to get more green squares by actively contributing to open source.

[0xPratyush]

Day 27

• Went through https://hacktoberfest.com/participation/ to get to know the best practices when participating in Hacktoberfest 2022.
• started exploring some projects and got couple of issues assigned.
• currently working on solving those issues and exploring some projects and communities on the github universe

[kuraakhilesh8230]

congrats you have completed milestone-3 successfully and you are good to go🎉

[0xPratyush]

Thanks @kuraakhilesh8230 .

[0xPratyush]

Day 28

• Working on previous issues assigned.
• looking for some great projects for hacktober fest.

[0xPratyush]

Day 29

UP voted project ideas Programming Club Discussion Website for College Students Scaler Discord Token Tracker

My idea

Progress tracker

[0xPratyush]

Day 30

So here it is, with a heavy heart commenting may be the last time on this issue.. successfully completed the 30days open source challenge. Day by day tasks were challenging and through this challenge, I learnt how to contribute , make a repository, make PR, create issues and use Git Bash or GitHub app. Thank you Scaler for organizing it, everyone in the community was helpful and encouraged a lot during these 30 days. And I am happy to say that now I am full of confidence and I will continue my journey of open source.

Thanks to all scaler stars and specially shivaylamba for this opportunity.

[Mrjoy832]

Milestone-4 done ✅