scaleracademy / scaler-september-open-source-challenge-2022

Scaler September Open Source Challenge
321 stars 345 forks source link

Challenge-11,14,16, 19,20,21, 23,24,25 #237

Open Mrjoy832 opened 2 years ago

Mrjoy832 commented 2 years ago

name: Tridib Bag github_user_name: Mrjoy832

Mrjoy832 commented 2 years ago

Ch-2

Link: https://github.com/Mrjoy832/scaler-september-open-source-challenge

image

Mrjoy832 commented 2 years ago

ch-3

image

Mrjoy832 commented 2 years ago

Ch-4

image

Mrjoy832 commented 2 years ago

Ch-9

image

image

Mrjoy832 commented 2 years ago

Challenge-11

image

Mrjoy832 commented 2 years ago

Challenge-13

image

image

DaltonDeven commented 2 years ago

✅ Good to go😎🤩

Mrjoy832 commented 2 years ago

✅ Good to go😎🤩

Pata hain 😤😤

Mrjoy832 commented 2 years ago

Challenge - 14

image image image image

Mrjoy832 commented 2 years ago

Ch-16

Resolved conflicts

image image

Mrjoy832 commented 2 years ago

New PR Link:

https://github.com/scaleracademy/scaler-september-open-source-challenge/pull/1117

Mrjoy832 commented 2 years ago

Challenge-17

image

image

image

image

image

Mrjoy832 commented 1 year ago

Ch-19

image

image

Mrjoy832 commented 1 year ago

Ch-20

project repo project board image image image

DaltonDeven commented 1 year ago

All Set To Go✅✅

Mrjoy832 commented 1 year ago

Ch-21

image

image

Mrjoy832 commented 1 year ago

Ch-23

PR{s)
Write descriptive and consistent names Create a clear PR title and description Keep PRs short (same applies to files and functions)

Branch(s)
The important branches in any project is the -Main - Stable version -Development - Where all the changes take place -QA - Where all the testing takes place 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. The name of these branches should match with the naming convention of the rest of the team.

Issue(s)

Always see for good-first-issue in the repos Avoid long descriptive names Create only meaningful issues

Mrjoy832 commented 1 year ago

CH-24

I am going to contribute into learnCPP which was under GSSOC'22. I am already assigned on this issue and going to start working on it. The issue: C++ code to find out cycle in a linked list. Link: https://github.com/Lakhankumawat/LearnCPP/issues/415

Mrjoy832 commented 1 year ago

Ch-25

I am assigned to an issue , start working and searching the solution of the issue https://github.com/Lakhankumawat/LearnCPP/issues/415

DaltonDeven commented 1 year ago

All Set To Go Verified for Milestone-3 Congrats👍

Mrjoy832 commented 1 year ago

Ch-26

image

Mrjoy832 commented 1 year ago

Ch-27

Hecktoberfest-2022

PR/MRs must be created between October 1 and October 31 and PRs must be made to public, unarchived repository. PR/MRs that their system detects as spammy will also not be counted. User with two or more spammy PR/MRs will be disqualified. PR/MRs must be tagged “HACKTOBERFEST” or must be labeled “HACKTOBERFEST-ACCEPTED". PR/MRs must not be labeled as "INVALID". PR/MRs Must be merged or have an overall approving review.

kuraakhilesh8230 commented 1 year ago

Not done challenge 28 29 and 30

Mrjoy832 commented 1 year ago

Ch-28