Challenges

[srijoy-paul]

name: Srijoy Paul github_user_name: srijoy-paul

[srijoy-paul]

URL of Forked repo: https://github.com/srijoy-paul/scaler-september-open-source-challenge-srijoypaul.git Screenshot:

[srijoy-paul]

Screenshot of all current branches in forked rep(locally) :

[srijoy-paul]

updated forked repo(locally):

Also updated the forked repo in github(remote): https://github.com/srijoy-paul/scaler-september-open-source-challenge-srijoypaul.git

[srijoy-paul]

Challenge 9:

Git reset the challenge 8 commit and push:

After reset:

[srijoy-paul]

Challenge 11 Created another branch:

[srijoy-paul]

Challenge 13: Using git stash

[srijoy-paul]

Challenge 14: Resolving merge conflicts :

[srijoy-paul]

Challenge 16: Conflict in PR:

Resolved the merge conflict in git:

After resolving the conflict:

[srijoy-paul]

Challenge 17: Using Github desktop

Downloaded Github Desktop and Created New Repo and Pushed to Github: Created new branch: Made changes in the README.md file and commit using github desktop from the feature branch: Push and Pull in github desktop: Pull Request: Squash and merge PR in github desktop:

[srijoy-paul]

Challenge 20: Working with project boards on github: Repository Link Project Board Link

[srijoy-paul]

Challenge 21: Creation and using aliases for git commands:

[kuraakhilesh8230]

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

[srijoy-paul]

Challenge 23: After reading the provided resources, the following are things that I learned and thought were significant:

• Appropriate methods of contribution and issue-raising:

1. Check the issue comments and labels before you begin any work to see whether somebody has already claimed it to work upon. to prevent any future conflicts.
2. Comment on it and say that you will be working on that issue.
3. Before submitting any pull requests, make sure your contribution adheres to the contributing.md file or the PR standards.
4. And if you discover any issue with the project, be sure to raise an issue.
5. And when you open a new issue or make a comment to work on one, be sure to add any potential solutions or strategies you have in mind.

• How to create a nice pull request effectively:

1. Try to be as clear as possible when naming your branches.
2. Give your PRs and commits descriptive titles, and it's usually advised to write them in the imperative tense (for example, "Add JS File" rather than "Added Js File") because this is how Github's inherently generated commits are written.
3. Adding a meaningful description to your PRs and commits is a follow-up to the second point. Give more information about the PR and Commit, as well as why they were opened.
4. Always stay current and check your feature branch for any conflicts or mistakes.
5. Try to lint your code files appropriately.

• Git branching and naming conventions: Regular branches and temporary branches are two examples of how git branches can be named to be more specific.

1. Git branching strategies allow separation of work.
2. Dev, master/main, and QA are the three main branches you should have in your repositories. Regular branches have fairly simple naming conventions.
3. Temporary branches are typically used to add features, resolve bugs, etc.
4. Some standard procedures are used for additional branches, such as short branch names, hyphens as branch separators, distinct branch ids, etc.
5. If there are other contributors besides you, it is preferable to prefix your branches with your name.
6. If there are numerous contributors or active branches, it can be useful to filter the branches.

[srijoy-paul]

Challenge 24: Finding suitable good first issues to contribute Status: I'm looking for problems to which I can contribute right now. I looked into a lot of them, however the majority of them seemed difficult ones according to that are currently outside the scope of my knowledge contribution. I've also looked some of the repositories of people I know. When I locate a significant issue to contribute, I will update this as soon as possible.

[srijoy-paul]

Challenge 24 update and Challenge 25 :

I found a issue to contribute on, and requested on the issue to assign me the task:

Maintainer assigned me the task: Working on this issue

Challenge 25:

A beginner's project in which people create a pull request by updating an HTML file and adding their information to it.

• Project LInk

• My PR Link

Waiting for Merge and after merge on their site it will show like this: On this site

[srijoy-paul]

Update Challenge 24:

• Created a pull request for the issue I was assigned.
• Pr link
• PR approved by maintainer and merged successfully.

[srijoy-paul]

Update for above comments

My Pull Request approved by the maintainer:

Changes of the contribution appeared on the project site :

[srijoy-paul]

Challenge 26:

• Found another repo which helps beginners in their contribution. Link

• Added my pr on that repo. Link

• I'm learning about the common guidelines they follow for issues and PRs by watching different repositories, such as naming, adding proper labels, mentioning the issue in the PR, and so on. The readme files are carefully designed for beginners to follow, covering every nook and cranny.

• And successfully registered for Hacktoberfest:

Created a open-source project repo with other discord members, for beginners to contribute : link

[srijoy-paul]

Challenge 27:

• [x] Gone through the resources provided in the hacktoberfest site.

• [x] I've also explored different repositories participating in hacktoberfest, which match my skill set, and talked with different maintainers in the hacktoberfest discord channel about how I can contribute to their project using the tech stacks I use.

Tips to follow for effective contrubution:

• For beginner-friendly tasks, look for issues labelled good-first-issue.

• Best sources for contributions made for the first timers:

  1. EddieHubCommunity/hacktoberfest-practice: Repo for you to raise a Pull Request for practice
  2. First Timers Only - Get involved in Open Source and commit code to your first project
  3. Up For Grabs (up-for-grabs.net)

• It should also be noted that contributions do not always consist of code but can also include writing documentation, design contributions, checking for issues in the project and raising an issue, and so on. So please feel free to contribute in any way you see fit.

• Look for the "hacktoberfest" label; repositories without the "hacktoberfest" label are not eligible for the event; and complete the challenge by submitting a total of four Pull Requests/Merge Requests between October 1 and October 31.

• Don't choose inactive repos for contribution if you're actively taking part in Hacktoberfest and want to finish the challenge. By inactive repos I mean ones that haven't been updated in recent months.

• Before contributing to any projects, always read the contributing.md or readme file. The majority of projects contain detailed documentation that includes information on the project, how to contribute, and all applicable rules, dos, and don'ts.

• Open Source is a broad term, and Hacktoberfest is simply a way to celebrate and get beginners started with Open Source by getting them used to these tools and instilling the spirit of open source in them. Make an effort to contribute actively whenever you feel something can be improved.

[srijoy-paul]

Challenge 28:

Contributions I made till now :

Update on Comment

• https://github.com/EddieHubCommunity/hacktoberfest-practice/pull/1859

• https://github.com/Syknapse/Contribute-To-This-Project/pull/1670

Collaborated with community members:

• https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/issues/149

• https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/pull/160

• https://github.com/PrakashGatiyala/60-seconds-of-cpp

[srijoy-paul]

Challenge 29:

• Shared my idea on discussions section: https://github.com/scaleracademy/open-source-projects/discussions/139

• Upvoted the existing ideas which I liked:

[srijoy-paul]

Challenge 30:

First and foremost, I'd like to thank Scaler for organizing such a fantastic event. All of the challenges were completed successfully. Folks in the community was extremely helpful and encouraging. Actually, this whole git and GitHub thing was completely new to me, and it was a great way to learn that. It would have taken much more time or can't be done that correctly in each step if done alone, but learning was exponential with the help of these challenges and the assistance of others. And also, I've made contributions to some projects.

I will continue contributing in open-source projects in future as well, and I'm especially excited for Hactoberfest because it will be my first time participating in any open-source event.

[kuraakhilesh8230]

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