Challenge 30/30 complete successfully

[vashuag]

name: Vashu Agarwal github_user_name: vashuag URL of your forked repository https://github.com/vashuag/scaler-september-open-source-challenge

A screenshot of the cloned project in your system

[vashuag]

Screenshot showing the list of all the current branches inside of your forked clone repository

[vashuag]

[vashuag]

e.png">

[vashuag]

Challenge 11 completed

[vashuag]

Challenge 13 completed

[DaltonDeven]

Thanks for putting in the effort we appreciate it very much, you can continue to take part in the challenge , but wont be eligible for the rewards because challenge 9,10 is not done correctly and there are lot of commits in PR

[vashuag]

Thanks for putting in the effort we appreciate it very much, you can continue to take part in the challenge , but wont be eligible for the rewards because challenge 9,10 is not done correctly and there are lot of commits in PR

Thank you, for letting me know my status. I have read on your terms, that if I complete the challenge for complete 30 days then irrespective of the issues , i will be eligible for rewards.

[vashuag]

Completed challenge 14 with merged and resolved conflicts

[vashuag]

Thank you, for letting me know my status.I have read on your terms, that if I complete the challenge for complete 30 days then irrespective of the issues , i will be eligible for rewards. Please let me know will i get any rewards later on . Although irrespective of that these 30 days are going to very knowledgable , thank you for opportunity.

Vashu Agarwal github username :vashuag

On Wed, 14 Sept 2022 at 22:56, DaltonDeven @.***> wrote:

Thanks for putting in the effort we appreciate it very much, you can continue to take part in the challenge , but wont be eligible for the rewards because challenge 9,10 is not done correctly and there are lot of commits in PR

— Reply to this email directly, view it on GitHub https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/425#issuecomment-1247084213, or unsubscribe https://github.com/notifications/unsubscribe-auth/AT6GST4HARQ5EHLJ6CMP7C3V6IDGDANCNFSM6AAAAAAQCS4PHE . You are receiving this because you authored the thread.Message ID: <scaleracademy/scaler-september-open-source-challenge/issues/425/1247084213 @github.com>

[vashuag]

Resolved conflict, Challenge 16 completed

[vashuag]

using git hub desktop and performing commit , merge ,push , pull

[vashuag]

Retrying challenge 9,10 as given in feedback

[vashuag]

challenge 20 using project board on github

[vashuag]

challenge 21 making git alias commands and using it

[kuraakhilesh8230]

challenge 20 using project board on github

Do challenge 20 correctly and attach screen shots of all the files of your project which should show done after moving from inprogress

[vashuag]

Redone challenge 20

[vashuag]

Challenge 23

Things to be done for effective Open Source Contribution:

Follow Standard Git Branching Naming Conventions , such as; start branch name with Group word • bug-logo-alignment-issue Using unique id : wip-8712-add-testing-module which makes possible to track the progress from external system Using Hyphen ,Slash or Underscore as Separators : feature_upgrade_jquery_version_loginmodule Using Author Name : _ Things to avoid while naming branches: Using Numbers only ,using all naming conventions simultaneously Making long descriptive names long-lived branches

For Making a better Pull Request

First and foremost , using above things for giving feature branch a clear name. Giving all PRs and commits a active and descriptive title and use present imperative tense Pls should be with meaningful description with Why the code necessary? How you are going to solve ? and What functionality added or changed? Whenever possible showing functionality visually giving reviewer the gist of work beforehand The most important thing is to review our own PR before assigning to others with running tests, linting and to caught up with latest changes

Working with issue Make sure to read labels properly some of the mean the following ; help wanted: Open to participation from the community but not necessarily beginner-friendly good first issue: Open to participation from the community and friendly towards new contributors staff only: Requires infrastructure access or institutional knowledge

issues not ready to work status: blocked: Blocked by other work that needs to be done first status: ticket work required: Needs additional work before it is ready to be taken up status: awaiting triage: Has not been triaged by a maintainer

If there is no label , add comment asking the maintainers to triage the issue .

Before actually starting work with any issue , check for comments /labels to see whether someone else has indicated that they are working on it

The Overall Contribution Process Comment on issue on which we are working write code and submit pull request wait for code review and address issue raised as soon as we can

Proposing a new issue

1. Create a new GitHub issue associated with the relevant repository and propose our change there .
2. The issue will automatically have the 🚦 status: awaiting triage label applied. Wait for a project maintainer to evaluate your issue and decide whether it's something that we will accept a pull request for.
3. Once the project maintainer has approved the issue and removed the 🚦 status: awaiting triage label, we may start work on code as described in the "Contribution process" section above.

[vashuag]

Challenge 24 Still looking for beginner friendly issue which I can feel confident to make changes in.Scrolled through various repos ,issues from the link provided in challenge https://goodfirstissue.dev/language/

[vashuag]

Challenge 25 Have looked for some beginner freindly issues on different repos and have commented on few to work on . waiting for responses and looking for registering on Hacktoberfest

[vashuag]

Challenge 26 Registered for Hacktober fest and started contributing to open source in beginner friendly projects

[DaltonDeven]

Verified for milestone-3

[vashuag]

Challenge 27 Some most important tips and rules are as follows:

1. The PRs and MRs should be in bound dates from 1 oct to 31 oct.
2. Anyone should not spam in any repos
3. Contributions with metioned /tagged "Hacktober fest " will be counted only.
4. Certain links for beginner friendly issues are given :https://github.com/firstcontributions/first-contributions
5. Follow Standard Git Branching Naming Conventions , such as; start branch name with Group word • bug-logo-alignment-issue Using unique id : wip-8712-add-testing-module which makes possible to track the progress from external system Using Hyphen ,Slash or Underscore as Separators : feature_upgrade_jquery_version_login_module Using Author Name : Things to avoid while naming branches: Using Numbers only ,using all naming conventions simultaneously Making long descriptive names long-lived branches

6.For Making a better Pull Request First and foremost , using above things for giving feature branch a clear name. Giving all PRs and commits a active and descriptive title and use present imperative tense Pls should be with meaningful description with Why the code necessary? How you are going to solve ? and What functionality added or changed? Whenever possible showing functionality visually giving reviewer the gist of work beforehand The most important thing is to review our own PR before assigning to others with running tests, linting and to caught up with latest changes

[vashuag]

Challenge 28

Tried a simple contribution of adding a card with full stack resources and merge successfully and under review . link to pr: https://github.com/Syknapse/Contribute-To-This-Project/pull/1702

[vashuag]

Challenge 29

Started a new discussion with idea of Ai Drones and upvoted some of the ideas I liked

[vashuag]

Challenge 30 Last Day of this Scaler Open Source Challenge , I literally learned and enjoyed a lot , in this event .Thank you Scalar for providing such an amazing opportunity just before the Hacktoberfest, which has given me confidence to contribute to open source on my own .Thank you @kuraakhilesh8230 @DaltonDeven @shivaylamba for checking and verifying my milestones , and giving me feedback for it . I will surely encourage others to contribute to open source and make world the better place ,and this community to grow

[Mrjoy832]

Milestone-4 done ✅