scaleracademy / scaler-open-source-september-challenge

335 stars 456 forks source link

Challenge #1 #20

Open SHAIK-MOHAMMED-JAVED opened 1 year ago

SHAIK-MOHAMMED-JAVED commented 1 year ago

name: SHAIK MOHAMMED JAVED github_user_name: SHAIK-MOHAMMED-JAVED discord_id: javedshaik

SHAIK-MOHAMMED-JAVED commented 1 year ago

URL of forked repository : https://github.com/SHAIK-MOHAMMED-JAVED/scaler-open-source-september-challenge.git Screenshot of the cloned repo in the system/PC : Screenshot (20)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 3 - creating branch and switching it. image

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 4 - Sync fork repo with original repo Screenshot (21) Screenshot (22) Screenshot (24) Screenshot (25)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 5 - push changes to github branch and create a PR to Original repo.

PR Link - https://github.com/scaleracademy/scaler-open-source-september-challenge/pull/657

image

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 6 - Add a new commit so that it should reflect in the PR which was created in Challenge 5. image

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 7 - Committed and Pushed the code to the PR, But it was unwanted commit, so removed the commit from the PR using 'git reset and git push -f'. Here are the steps.

Screenshot (27) Screenshot (28) Screenshot (29) Screenshot (30) Screenshot (31)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 8 - Create a new branch, add a file, and push it to remote. image

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 9 - Rebasing the commits in the branch to eliminate unuseful commits reflect in main branch NOTE: if you face errror -> [error: cannot 'squash' without a previous commit] make first line of commit as pick in VIM Editor and make remaining commits to squash. Commands of VIM Editor:

To insert -> i To exit insert mode -> esc To save and exit the file -> :wq (or) :q!

Commands to Rebase:(using interactive mode using squash)

git log --oneline -> to see the commits in current branch git rebase -i HEAD~3 -> [ i represents interactive mode, head~3 means rebase last 3 commits from current cummit]

Screenshot (33) Screenshot (34) Screenshot (37) Screenshot (38) Screenshot (40) Screenshot (41) Screenshot (42)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 10 - Rebasing the commit to reflect in PR. Screenshot (43) Screenshot (44) Screenshot (45) Screenshot (47) Screenshot (48) Screenshot (49) Screenshot (50) Screenshot (51) Screenshot (52)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 11 - Statshing the changes that are staged and removing them. image

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 12 -Today's challenge is based on the concept of signing your commits To set up gpg key,

  1. Download Kleopatra (GPG).
  2. Follow the below link.
  3. Go to the GitHub profile and add gpg public key. once done (from then it will show verified) vimp reference link - https://tau.gr/posts/2018-06-29-how-to-set-up-signing-commits-with-git/

Screenshot (64) Screenshot (66)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 13 - Creating Gists Screenshot (68) Screenshot (69)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 14 - Working on git-rebase. -> Sql commit, Angular commit, and Vue commit are separately committed. -> Combining all the commits into one using the rebase command. Screenshot (70) Screenshot (72) Screenshot (76) Screenshot (78) Screenshot (79) Screenshot (80) Screenshot (87)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 15 - Resolving merge conflicts. Screenshot (88) Screenshot (89) Screenshot (90) Screenshot (92)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 16 - Adding lines to challengers-list.md file, To recreate merge conflict. Screenshot (93) Screenshot (94) Screenshot (95)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 17 - Resolving locally occurred Merge conflicts Screenshot (96) Screenshot (97) Screenshot (98) in the PR.

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 18 - GitHub GUI INSTALLATION AND USAGE. -> Added account to GitHub GUI. -> Created a repo using GUI. -> Added a file to the main branch. -> Pushed to remote repo. -> Created a branch named new-feature from main. -> Added some content in the same file. -> Created a PR to main from the new-feature branch. -> Pulled and Merged the PR in main. Screenshot (100) Screenshot (101) Screenshot (102) Screenshot (104) Screenshot (105) Screenshot (107) Screenshot (109)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 19 - Hands-on on Github CodeSpace ++++++ We can do operations on our code using CodeSpace without depending on IDE. It is fast as we won't clone on our HDD. We can perform all git ops online in the terminal. +++++ Screenshot (110) Screenshot (111) Screenshot (114) Screenshot (113) Screenshot (115)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 20 - Creation of GitHub Actions. Added file named lint.yml to newly created repo. A little bit to focus more on the content of the lint.yml file. Screenshot (124)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 21 - Creation of Project Board. Assigned and integrated with Repo to create as an issue. Screenshot (125) Screenshot (126)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 22 - Creating Alias for Git commands git fu -> git fetch upstream git mu -> git merge upstream/main

These two aliases are created. Screenshot (128) Screenshot (129)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 23 - Hosting Github static portfolio Page.

Screenshot (130) Screenshot (131) Screenshot (133)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 24 - Overview of the guidelines/best practices/rules/ recommendations to follow while contributing to open-source projects.

-> Always follow the instructions mentioned in the pre-read file. -> Follow the folder structure as present in the project for ease of use. -> Identify the work that you need to contribute. -> Create the meaning full branch name so that it should represent the feature name/work. -> Commits committing to the upstream branch should be meaningful and precise. -> Always sign off in your commit. -> Create a PR with the upstream branch from your working branch.

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 25 - To contribute realtime repository. Status - Looking for repository.

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 26 - I have found the repo to contribute to open source. issue link: https://github.com/nikohoffren/fork-commit-merge/issues/638

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 27 - I raised a pull request for the Open Source project. My First Contribution to the Open Source was successfully merged.

PR LINK

I registered for OpenQuest and Looking for Teammate.

Todays Task:

Cherry-picking => Process of adding a few commits to another branch instead of merging the whole branch into another. -> Created two branches named branchA and branchB in the Make_Hands_Dirty_By_Code repo. -> Added feature1, feature2, feature3 in branchA. -> cherry-picked feature1 and feature2 from branchA to branchB. -> pushed changes to the remote.

Screenshot (135) Screenshot (136) Screenshot (137) Screenshot (140) Screenshot (141)

SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 28 - UPDATES

  1. Registered for OpenQuest, In search of a Teammate.
  2. Contributed to open source and shared details to help other fellow learners find open source repos. (Comment)[https://discord.com/channels/780066247601291285/787377926722945035/1156958046820499537].
  3. Registered for HacktoberFest.
SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 29 - Creating a Profile in GITHUB.

  1. Registered for OpenQuest, Looking for Teammate.
  2. Created a basic GitHub profile.
SHAIK-MOHAMMED-JAVED commented 1 year ago

Day 30 -

Registered for OpenQuest but looking for a teammate to make a team.

NeverExpected

I didn't think I would reach this day with continuous #learning along with #Consistency. It will be a remarkable journey and I will be cherishing these moments. I thank Scaler for giving me this opportunity. Special thanks to Shivay for posting challenges keeping the participants engaged and making us solve a challenge every day consistently.

Last, but not least, it is just a beginning to be #Consistent.

image