Challenge - 1

[anishaga]

name: Anish github_user_name: anishaga

[anishaga]

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

[anishaga]

[anishaga]

[anishaga]

[anishaga]

[anishaga]

[anishaga]

[anishaga]

[anishaga]

[anishaga]

[anishaga]

[anishaga]

[anishaga]

[anishaga]

[anishaga]

[anishaga]

Project Link : https://github.com/users/anishaga/projects/3 Repo Link: https://github.com/anishaga/Tic-Tac-Toe Github Board: Game:

[anishaga]

[kuraakhilesh8230]

Project Link : https://github.com/users/anishaga/projects/2

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

[anishaga]

Project Link : https://github.com/users/anishaga/projects/2

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

I didn't understood the task earlier, have updated now: https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/62#issuecomment-1252303800

[anishaga]

Website: https://anishaga.github.io/Personal-Website/ Repo: https://github.com/anishaga/Personal-Website

[anishaga]

Things I understood and found important after going through the resources provided are:

-- Guidelines to follow for issue:

• If you spot a problem search if an issue already exists .If a related issue doesn't exist, new issue can be created using a
• relevant issue form.
• New issue created should have clear purpose.
• Scan through existing issues to find one that interests you. search can be narrowed using labels as filters like easy difficulty
• task, question ,etc.
• Comment on it and say you're working on that issue. to avoid conflicts with others also working on the issue.

-- Guidelines to follow for BRANCH creation:

• Branch are mostly of two types Regular(permanent bases) & Temporary Branches(fixing or new feature).
• Branch name should have a Group word like bug/WIP.
• Unique IDs in branch names.
• Use Hyphen or Slash as Separators for easy reading.
• Branch with Author Name.
• Avoid long descriptive names for branches.

-- Guidelines to follow for pull request:

• Give your commits and PRs descriptive titles.
• Meaningful description.
• Show your functionality visually, whenever possible like adding screenshots.
• Link PR to issue if you are solving one.