Challenge (30/30)

[sreejasaha19]

name: Sreeja Saha github_user_name: sreejasaha19

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

A screenshot of the cloned project in your system

[sreejasaha19]

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

A screenshot of the cloned project in your system:

[sreejasaha19]

URL: https://github.com/sreejasaha19/scaler-september-open-source-challenge/branches

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

[sreejasaha19]

Screenshot showing the latest repository contents:

[sreejasaha19]

Challenge 9:

[sreejasaha19]

Challenge 10:

[sreejasaha19]

Challenge 11: Share screenshot of this new branch in the issue created in previous challenge:

[sreejasaha19]

Challenge 13:

[sreejasaha19]

Challenge 14: Share appropriate screenshot in the issue created in the first challenge

[sreejasaha19]

Challenge 16: share screenshot:

[sreejasaha19]

Challenge 17: Repository link : https://github.com/sreejasaha19/Github-Desktop-Demo/tree/main

Download GitHub desktop:

Create a new repository in github:

Create new file:

Added details in README.md to my repo:

Published repo on remote:

Create new branch:

Publish to Github:

Open a Pull request pull request link and merge it: https://github.com/sreejasaha19/Github-Desktop-Demo/pull/1

[sreejasaha19]

Challenge 20:

GitHub repository Link for my project : [VISIT HERE](https://github.com/sreejasaha19/Demo-Project) Created a Project Board for my repository: [VISIT HERE](https://github.com/users/sreejasaha19/projects/1/views/1)

Step 1 : Project board created Step 2 : Issues created Step 3: Issue in progress Step 4: Issue in done Step 5: Closed Issues

[sreejasaha19]

Challenge 21:

Screenshot of alias created:

Screenshot of using alias:

[kuraakhilesh8230]

Challenge 20:

GitHub repository Link for my project : [VISIT HERE](https://github.com/sreejasaha19/Demo-Project) Created a Project Board for my repository: [VISIT HERE](https://github.com/users/sreejasaha19/projects/1/views/1)

do challenge-20 correctly because all the screen shots should be attached starting from todo to done and in atlast the screen shot should show done with tick marks for all the files complete this by sunday

[sreejasaha19]

Challenge 20:

GitHub repository Link for my project : [VISIT HERE](https://github.com/sreejasaha19/Demo-Project) Created a Project Board for my repository: [VISIT HERE](https://github.com/users/sreejasaha19/projects/1/views/1)

do challenge-20 correctly because all the screen shots should be attached starting from todo to done and in atlast the screen shot should show done with tick marks for all the files complete this by sunday

I have done it. Please review it.

[sreejasaha19]

Challenge 23 :

This is challenge 23. Some good practice tips for open-source. This is the basic summary tips for the open source .

Branches

1. Regular Branches : There should be 3 permanent base branch - master , dev and QA. The names signifies their purpose.
2. Start branch name with group word - your branch name should have the category/group tag you are working with. For example : while fixing a bug, the syntax should be --> group_tag-<your_branchName>.
3. Using tracker ID in a branch would be ideal way to track the working tree .
4. Using of the /as separators increases the readability and avoid confusion.
5. You can add your name to the branch to signify your bug fixes. Note : avoid using long names , which might increase confusion".

Pull Request

1. Give your PR s descriptive title to make other easy to track your working tree.
2. Streamline your process of creating a new PR.
3. PR should gave some meaningful descriptions as it reduces time and complexity of your work and also decrease confusion.
4. Show your functionality visually, whenever possible.

Issues

1. If you are a beginner start with a good-first-issue issue tag.
2. If you want to work on a issue, then comment on that **you want to work on that issue".Wait for the review and check for another issue as soon as possible.
3. Create a GitHub issue with the relevant repository and propose your change there. Note : Make sure that you proposed a relevant issue on your repository.

[kuraakhilesh8230]

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

[sreejasaha19]

Challenge 24:

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

1. Issue Link :VISIT HERE

[sreejasaha19]

Challenge 25 :

Today, I had successfully contributed to the task assign in challenge 24 Pull request link: https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/pull/173

[sreejasaha19]

Challenge 26 :

register today for https://hacktoberfest.com/:

I found an issue that is suitable for me and also got an approval to work on that for hacktoberfest : VISIT HERE

[sreejasaha19]

Challenge 27 :

Why Hacktoberfest?

• To encourage first time contributors to make meaningful contributions to the community.
• To spread awareness about open-source communities.

How to contribute

• Find repositories which we like and understand and find where you can contribute.
• Find a issue you can work on.
• Fork the repo, clone it to the local system and create a new branch.
• Make the changes you want to make in this branch and push it to the remote repository.
• Submit a pull request from this branch to the upstream branch.
• Wait for verification, resolve any issues pointed out by the code maintainers.
• If the contribution solves the issue, then the pull request is merged.

Tips for Hacktoberfest

• Solve issues for the repositories having the hacktoberfest tag for the pull request to be counted for the challenge.
• For first time contributors, find issues having the good first issue tag to find contributors suitable for newbies.
• Contribute to repositories which only add value to the community, and not the ones that encourage easy contributions meant purely for the sake of new users learning how the open-source workflow works.
• For the contributions to count for the hacktoberfest, all pull/merge requests must be submitted from October 1-30.
• Make atleast 4 valid pull requests to complete Hacktoberfest.
• Avoid submitting low quality pull requests/spammy PRs.
• QUANTITY IS FUN, QUALITY IS KEY
• Open Source is not just about learning Github and contributing for the sake of it, it is more like learning, connecting with developers and helping each other.

[DaltonDeven]

All Set To Go Verified for Milestone-3 Congrats👍

[sreejasaha19]

Challenge 28 :

PR Request Link: https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/pull/173

[sreejasaha19]

Challenge 29 :

Upvoted Ideas:

https://github.com/scaleracademy/open-source-projects/discussions/45#discussioncomment-3767068

My Idea:

https://github.com/scaleracademy/open-source-projects/discussions/141

[sreejasaha19]

Challenge 30 :

• I've completed all the challenges.

Hacktoberfest

I'm excited about Hacktoberfest. I will try to contribute beyond the Hacktoberfest.

Experience of this initiative.

• It was a great initiative. Special thanks to Scaler Team for organizing it for beginner.

• I've learn lot of new things from this Open Source challenge. Like most common used cmds for git, github pages, github gist etc.

• 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.

Thank you Scaler Discord Team.

[kuraakhilesh8230]

Congratulations you have successfully completed milestone 4 🎊