All_Challenges - ShreyanshKhaitan - shrey141102

[shrey141102]

Completed <Task 1>

name: Shreyansh Khaitan github_user_name: shrey141102 discord_id: shrey

[shrey141102]

Completed <Task 2>

Forked the repository using the Github UI of the original repository Cloned the forked repository in the local system using git clone https://github.com/shrey141102/scaler-open-source-september-challenge

URL of forked repository

[shrey141102]

Completed <Task 3> Created the new branch named mrudangvora-details using the command git branch shrey141102-details

The attached screenshot shows the list of all the current branches inside the local forked clone repository

[shrey141102]

Completed <Task 4>

git remote -v Configured the forked repository with the original repository using git remote add upstream Fetched the branches from the original repo to the local forked repo using git fetch upstream Checkout the forked repo branch which needs to be synced using git checkout main and git checkout shrey141102-details Sync the changes from the upstream branch to the forked repo branches using git merge upstream/main

Finally do this - git push origin main and git push origin shrey141102-details This will commit changes to your forked repo.

[shrey141102]

Completed <Task 5>

Here is the screenshot

[shrey141102]

Completed <Task 6>

[shrey141102]

Completed <Task 7>

link to PR

used commands -> git reset --hard commit-id-to-remove and git push -f origin your-branch-name

but for this you need to first see logs using git log

from here you can find commit ID.

[shrey141102]

Twitter post - https://twitter.com/__shrey__14/status/1700048541014806716

[shrey141102]

Completed <Task 8>

Had to create a file and push it in the forked repo https://github.com/shrey141102/scaler-open-source-september-challenge/tree/challenge8

[shrey141102]

Completed <Task 9>

[shrey141102]

completed Task 10

https://github.com/scaleracademy/scaler-open-source-september-challenge/pull/573

here you can see the commit for challenge 10

[shrey141102]

Completed Task 11

[shrey141102]

Completed Task 12

Here's the PR https://github.com/scaleracademy/scaler-open-source-september-challenge/pull/573

there are no conflicts now all checks passed

[shrey141102]

Completed Task 13

Add URLs of the gists

[shrey141102]

Completed task 14

[shrey141102]

Twitter post week 2 - https://twitter.com/__shrey__14/status/1702937903117328425

[shrey141102]

Completed <Task 15>

[shrey141102]

Task 16 done

terminal commands

you can see PR here

[shrey141102]

Task 17 done

Didn't get any conflicts :')

[shrey141102]

Completed Task 18

added files to a repo

committed files

pushed to origin

Files are here

[shrey141102]

Completed Task 19

explored github codespaces Looks very similar to VSCode

Made changes to readme file and pushed changes

It is a great tool for coding and editing but lags a bit since its on browser.

[shrey141102]

Completed Task 20 - Set Up a GitHub Action for Code Linting

So far so good but how do I pass these checks and make code lint free??

[shrey141102]

Task 21 Done

[shrey141102]

Task 22 completed

created alias for brach, checkout, commit

[shrey141102]

Task 23 done

[shrey141102]

Completed <Task 24>

1. Read about CONTRIBUTING.md file and understood the basic steps for making any contribution.
   • Create an issue or work on existing issue
   • Clone the repo
   • Create the feature / issue branch
   • Make the changes
   • Create a Pull Request
   • Work on the review comments and ask for approval
   • Once approved, merge the PR and resolve conflicts of any
   • Delete the branch created in the above steps.
2. Branching naming conventions: We have 2 types of branches: Regular & Temporary
   • Regular Branches: These branches are available in the repository on a permanent basis. Eg: main, dev, qa
   • Temporary Branches: These are branches that are created for a purpose and then deleted once their purpose is completed. They can be as follows: -- Bug Fix -- Hot Fix -- Feature branch -- POC

Steps:

• Having worked with over 500 deliverables in the past 8 years, have found the following conventions useful: <branch-type>-<issue or ticket-number>-<brief-description> Eg: Feature-T432-Add-Email-Field
• Once the feature is completed, we can raise PR with the same branch name prefixed by PR- eg: PR-Feature-T432-Add-Email-Field
• We can add the description of the change in brief too.
• We can add the video snippet/images which makes it easier for the approver to approve the PR.
• Finally, once PR is approved and merged we can delete this temporary branch.

ABOUT FIRST CONTRIBUTIONS: Check tags - help wanted or good first issue to initiate the contribution journey

Other Web references: https://www.firsttimersonly.com/ https://goodfirstissue.dev/ https://firstcontributions.github.io/

Have done a few open-source contributions and looking forward to do more.

[shrey141102]

<Task 25>

I still haven't found a repository with a beginner level issue that I can contribute to. Actively looking

[shrey141102]

<Task 26>

Registered for the hackathon. Looking for a teammate. I think I will start some open source projects for colaboration.

[shrey141102]

Task 27 Done

uploading files in branchA

cherry-pick done

[shrey141102]

Task 28

registered for hacktoberfest registered for scaler open source hackathon

have created a repo for people to contribute to https://github.com/shrey141102/Javascript-projects

[shrey141102]

Task 29

have created my discord profile

[shrey141102]

done task 30

filled the google form for milestone-4

searching for repos to contribute to ready for hacktoberfest 🔥🔥