Skip to content
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.

Scaler Open Source Challenges (1-30) #233

Open
manmohan4142 opened this issue Sep 1, 2022 · 19 comments
Open

Scaler Open Source Challenges (1-30) #233

manmohan4142 opened this issue Sep 1, 2022 · 19 comments

Comments

@manmohan4142
Copy link

manmohan4142 commented Sep 1, 2022

Challenge 1 :

name: Manmohan Dhal
github_user_name: manmohan4142

Challenge 2 :

URL of your forked repository : https://github.com/manmohan4142/scaler-september-open-source-challenge

A screenshot of the cloned project in your system :
Screenshot (341)

@manmohan4142 manmohan4142 changed the title Challenge 1 Challenge 1 & Challenge 2 Sep 2, 2022
@manmohan4142 manmohan4142 changed the title Challenge 1 & Challenge 2 Challenge 1 & 2 & 3 Sep 3, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 3, 2022

Challenge 3 :

name: Manmohan Dhal
github_user_name: manmohan4142

URL of your forked repository : https://github.com/manmohan4142/scaler-september-open-source-challenge

Screenshot Of All Current Branches :

Screenshot (344)
Screenshot (343)

@manmohan4142 manmohan4142 changed the title Challenge 1 & 2 & 3 Challenge 1 ,2 ,3, 4 Sep 4, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 4, 2022

Challenge 4 :

name: Manmohan Dhal
github_user_name: manmohan4142

Screenshot showing the latest repository contents :
Screenshot (346)

Screenshot (354)

@manmohan4142
Copy link
Author

manmohan4142 commented Sep 9, 2022

Challenge 9 :

  1. Identify the commit id that needs to be removed (you should have created this in the 8th Challenge)
  2. Use git reset and force push, to remove the commit from your pull request.
  3. Share a screenshot of this, in the issue you created in previous challenges.

Screenshot (357)

@manmohan4142 manmohan4142 changed the title Challenge 1 ,2 ,3, 4 Challenge 1 to 9 Submission Sep 9, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 11, 2022

Challenge 11 :

  1. Create another branch from your current branch created in previous challenges (Don't create a new branch from main).
  2. Share screenshot of this new branch in the issue created in previous challenge

Screenshot (362)
Screenshot (363)

@manmohan4142 manmohan4142 changed the title Challenge 1 to 9 Submission Challenge 1 to 4 & 9 & 11 Submission Sep 11, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 13, 2022

Challenge 13 :

  1. Inside the branch you created in the previous challenge your-username-details create a new file inside the
    contributors/<YOUR-GITHUB_USERNAME>/ directory.
  2. Use the git stash command to move these changes to the stash area
  3. Delete the content from the stash area and share a screenshot of this inside the Github issue you created in the first
    challenge

Screenshot (369)

@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 & 9 & 11 Submission Challenge 1 to 4 , 9 , 11 , 13 Submission Sep 13, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 14, 2022

Challenge 14 :

  1. Follow the article shared above and try to reproduce a case of merge conflict in your system for a project and try to resolve
    it
  2. Share appropriate screenshot in the issue created in the first challenge.

Screenshot (376)
Screenshot (377)

@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 Submission Sep 14, 2022
@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 Submission Sep 16, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 16, 2022

Challenge 16 :

  1. You will notice that your pull request will have a conflict:
  2. Try to resolve this merge conflict using local git.
  3. Once resolved, share screenshot on the github issue created in the previous challenges

Screenshot (387)
Screenshot (388)

Screenshot (389)
Screenshot (394)
Screenshot (392)

@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 18 Submission Sep 18, 2022
@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 18 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 Submission Sep 18, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 18, 2022

Challenge 17 :

  1. Download GitHub desktop

Screenshot (406)

  1. Create a new repository on GitHub

Screenshot (407)

  1. Added & Edited the file

Screenshot (409)

  1. Commit New File

Screenshot (410)

  1. Publish A Repository

Screenshot (411)

  1. Publish New Branch & Created New Pull Request

Screenshot (413)

  1. Pull Request

Screenshot (415)

@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 Submission Sep 20, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 20, 2022

Challenge 20 :

  1. Take a screenshot of your project board for when you moved an card from In progress to Done
  2. Add you screenshot to the Github issue created in the previous challenges

GitHub repository Link for my project : https://github.com/manmohan4142/Challenge-20
Created a Project Board for my repository: https://github.com/users/manmohan4142/projects/1/views/1

Screenshot (464)
Screenshot (465)
Screenshot (466)

@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21 Submission Sep 21, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 21, 2022

Challenge 21 :

Screenshot of alias created :

Screenshot (459)
Screenshot (458)

@manmohan4142
Copy link
Author

Challenge 23 :

Things Which I understood and found important after going through the resources provided are :

  • Guidelines to be followed for Issue :

  1. New issue created should have clear purpose.
  2. Avoid long descriptive names.
  3. Comment on it and say you're working on that issue. to avoid conflicts with others also working on the issue.
  4. Create issues which are meaningful for us.
  • Guidelines to be followed for Branch Creation :

  1. Branch are mostly of two types Regular & Temporary Branches.
  2. Branch with Author Name.
  3. Unique IDs in branch names.
  4. The branches we will be working on has to be named as per a standard. For example, the branch name can include words
    like bug, fix, WIP, etc.. the issue it will be solving, author name, etc.
  • Guidelines to be followed for Pull Request :

  1. Give your feature branch a clear name.
  2. Give your commits and PRs descriptive titles.
  3. Show your functionality visually, whenever possible like adding screenshots.
  4. Show your functionality visually, whenever possible.

@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 Submission Sep 23, 2022
@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 Submission Sep 25, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 25, 2022

Challenge 24 :

After a lot of research I found an issue that is suitable for me and also got an approval to work on that.

Screenshot (472)

@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 , 25 Submission Sep 25, 2022
@manmohan4142
Copy link
Author

Challenge 25 :

  • Found a begineer opensource project to create a pull request and updating the html file.

  • Forked Repository Link : VISIT HERE

  • Pull Request got approved and merged Link : VISIT HERE

Screenshot (477)

  • Card which appear in GitHub PR Link : VISIT HERE

Screenshot (481)
Screenshot (482)

@manmohan4142
Copy link
Author

manmohan4142 commented Sep 26, 2022

Challenge 26 :

  • Finally Registered for Hactoberfest 2022 : Click Here

Screenshot (491)

  • Regarding the Issues , I have been assigned 4 issues which I am working on it and will update here after got merged.

@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 , 25 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 , 25 , 26 Submission Sep 26, 2022
@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 , 25 , 26 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 , 25 , 26 , 27 Submission Sep 27, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 27, 2022

Challenge 27 :

Some tips regarding Hactoberfest 2022 when Participating :

  • Hactoberfest is to encourage first time contributors to make meaningful contributions to the community.
  • To spread awareness about open-source communities.
  • Register anytime between September 26 and October 31.
  • Pull requests can be made in any GitHub or GITLAB hosted project that’s participating in Hacktoberfest.
  • Project maintainers must accept your pull/merge requests for them to count toward our total.
  • Have 4 pull/merge requests accepted between October 1 and October 31 to complete Hacktoberfest.
  • Only first 40,000 participants (maintainers and contributors) who complete Hacktoberfest can elect to receive one of two prizes: a tree planted in their name, or the Hacktoberfest 2022 t-shirt.
  • Avoid Submitting Low quality Pull/Merge Requests.
  • Spammy Pull/Merge Requests will be labeled as “SPAM.”

@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 , 25 , 26 , 27 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 , 25 , 26 , 27, 28 Submission Sep 28, 2022
@manmohan4142
Copy link
Author

manmohan4142 commented Sep 28, 2022

Challenge 28 :

Current Status of Contributing to Open Source:

Screenshot (498)

Screenshot (509)

@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 , 25 , 26 , 27, 28 Submission Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 , 25 , 26 , 27, 28 , 29 Submission Sep 29, 2022
@manmohan4142
Copy link
Author

@manmohan4142 manmohan4142 changed the title Challenge 1 to 4 , 9 , 11 , 13 , 14 , 16 , 17 , 20 , 21, 23 , 24 , 25 , 26 , 27, 28 , 29 Submission Scaler Open Source Challenges (1-30) Sep 30, 2022
@manmohan4142
Copy link
Author

Challenge 30 :

Finally!!! the day come this is the last step towards this September Open Source Challenge by Scaler ❤

First of all I have learnt how to contribute in open source and also about how to use github or git. Thanks to Scaler academy for organizing such an amazing and very informative challenge. This challenge helped me to learn so many basic commands of github not just for personal work level, but also for some professional level (For team projects). Each challenge was very helpful and 80% of them were new to me, I am glad that now I can use my learnings while contributing to projects.

So, now the Hactoberfest is coming I am glad to participate in this program and gain more knowledge for the future purpose .

@kuraakhilesh8230
Copy link

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants