Challenge 1-30

[Adyasha28]

name: Adyasha Samal github_user_name: Adyasha28

[Adyasha28]

Forked Repo URL- https://github.com/Adyasha28/scaler-september-open-source-challenge

[Adyasha28]

[Adyasha28]

challenge 4

[Adyasha28]

Challenge 9 :-

[Adyasha28]

[Adyasha28]

challenge-13

[Adyasha28]

Challenge-14

Created Merge Conflict Resolved merge conflict Changes in text file

[Adyasha28]

Challenge 16

[Adyasha28]

Challenge-17

CREATED new_repository_2 repo with a new branch child :

CREATED README.md :

PUSHED origin and RAISED a PR from child branch to main :

GitHub Repo new_repository_2 :

[Adyasha28]

Challenge 20:

Project:- Pooja Box Clone

Issue link: pooja-box-clone

[Adyasha28]

Challenge 21:-

[kuraakhilesh8230]

Challenge 20:

Project:- Pooja Box Clone

Issue link: pooja-box-clone

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

[Adyasha28]

Challenge: 23

The repository must have Development(dev), Master(master), and QA(QA) branches on permanent bases. Create Temporary Git Branches as per requirements, they can be deleted whenever needed. For example:- • Bug Fix • Hot Fix • Feature Branches • Experimental Branches • WIP branches

Git Branch naming convention for open-source contribution, • Start branch name with a group word • Use unique id on branch names • Use hyphen or slash as separators • Git branch with author name • Avoid using numbers only • Avoid long descriptive names for long-lived branches

Creating a good pull request • Give the feature branch a clear name • Give the commits and PRs active and descriptive titles • Streamline the process of creating a new PR • Give the PR a meaningful description • Show the functionality visually, whenever possible • Review your own PR before you assign it to others

Finding an issue • Issues available for community contribution: • The following tags mark issues that are open for community contribution:  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

• Issues not available for community contribution: o The following tags mark issues that are not open for community contribution:  🔒 staff only: Requires infrastructure access or institutional knowledge that would be impractical to provide to the community • Issues not ready for work: o The following tags mark issues that are not open for community contribution:  🚧 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

• Issues without any of the above labels: o These issues may (or may not) be open for contribution. o Please add a comment asking one of the maintainers to triage the issue and label it as appropriate.

[kuraakhilesh8230]

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

[Adyasha28]

Challenge 24:-

Requested to work on this issue

[Adyasha28]

Challenge 25:

-Got assigned with an issue: kadane-algo

-Created a PR for resolving the issue:

-PR was accepted and got good-first-issue label

[Adyasha28]

Challenge 26:

Registered for Hacktoberfest 2022:

[Adyasha28]

Challenge 27:

Some tips for Hacktoberfest-2022:-

• Pull requests can be made in any GITHUB or GITLAB hosted project that’s participating in Hacktoberfest.
• We need to submit at least for 4PRs to complete Hacktoberfest.
• Project maintainers must accept our pull/merge requests for them to count toward our total.
• We need to follow the Hacktoberfest guidelines and rules thoroughly.
• Avoid contributing to low quality issues/tasks.

[kuraakhilesh8230]

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

[Adyasha28]

Challenge 28:

Contributed to these Respositories:- first-contributions kadane's Algorithm Adyasha's Card

[Adyasha28]

Challenge 29:

UPVOTED some of the project ideas in the discussion:

Programming club discussion website DSA basket Portal for all interview experiences with question approaches, editorials, practice link(company specific)

[Adyasha28]

Challenge 30:-

I am thankful to Scalar discord for the Scalar-September-open-source-challenge . I got to learn a lot especially about git and github. Open source was really great. Looking forward for more such opportunities ahead.

[kuraakhilesh8230]

congrats you have successfully completed milestone-4 🎊