Skip to content
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.

Challenge (30/30) : anishcode19 #183

Open
anishcode19 opened this issue Sep 1, 2022 · 21 comments
Open

Challenge (30/30) : anishcode19 #183

anishcode19 opened this issue Sep 1, 2022 · 21 comments

Comments

@anishcode19
Copy link

name: Anish Kumar
github_user_name: anishcode19

@anishcode19
Copy link
Author

@anishcode19 anishcode19 changed the title Challenge-1 Challenge-1,2 Sep 2, 2022
@anishcode19
Copy link
Author

day-3

@anishcode19 anishcode19 changed the title Challenge-1,2 Challenge (3/30) : anishcode19 Sep 3, 2022
@anishcode19
Copy link
Author

day-4
day-4-c

@anishcode19 anishcode19 changed the title Challenge (3/30) : anishcode19 Challenge (4/30) : anishcode19 Sep 4, 2022
@anishcode19
Copy link
Author

Uploading day-9.png…

@anishcode19 anishcode19 changed the title Challenge (4/30) : anishcode19 Challenge (9/30) : anishcode19 Sep 9, 2022
@anishcode19
Copy link
Author

day-11

@anishcode19 anishcode19 changed the title Challenge (9/30) : anishcode19 Challenge (11/30) : anishcode19 Sep 11, 2022
@anishcode19
Copy link
Author

day-13

@anishcode19 anishcode19 changed the title Challenge (11/30) : anishcode19 Challenge (13/30) : anishcode19 Sep 13, 2022
@anishcode19
Copy link
Author

day-14-a
day-14-b
day-14-c
day-14-d

@anishcode19 anishcode19 changed the title Challenge (13/30) : anishcode19 Challenge (14/30) : anishcode19 Sep 14, 2022
@anishcode19
Copy link
Author

1

@anishcode19 anishcode19 changed the title Challenge (14/30) : anishcode19 Challenge (17/30) : anishcode19 Sep 18, 2022
@anishcode19
Copy link
Author

day-20
day-20-b
day-20-c

@anishcode19 anishcode19 changed the title Challenge (17/30) : anishcode19 Challenge (20/30) : anishcode19 Sep 20, 2022
@anishcode19
Copy link
Author

day-21
day-21-b

@anishcode19 anishcode19 changed the title Challenge (20/30) : anishcode19 Challenge (21/30) : anishcode19 Sep 21, 2022
@anishcode19
Copy link
Author

anishcode19 commented Sep 23, 2022

#Challenge 23 : Summary

Branches

  • Broadly, git branches are divided into two categories: Regular & Temporary Branches.
  • Regular Branches : There should be 3 permanent base branch - master , development and QA. The names signifies their purpose.
  • Start branch name with a Group word : By looking at the branch name, can understand what this Git branch is about and its purpose.
  • For example : while fixing a bug, the syntax should be --> group_tag-<your_branchName>
  • Using tracker ID in a branch would be ideal way to track the working tree .
  • Using of the / as separators increases the readability and avoid confusion.
  • You can add your name to the branch to signify your bug fixes.
  • Note : avoid using long names , which might increase confusion".

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:

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

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

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

Pull Request

  • Give your feature branch a clear name.
  • Give your commits and PRs descriptive titles.
  • Show your functionality visually, whenever possible like adding screenshots.
  • Show your functionality visually, whenever possible.

@anishcode19 anishcode19 changed the title Challenge (21/30) : anishcode19 Challenge (23/30) : anishcode19 Sep 23, 2022
@anishcode19
Copy link
Author

Challenge-24

Still looking for a GitHub repo to find relevant issues where I could actually contribute but didn't find any for now. I will continue looking and possibly find one that I can actually solve.

@anishcode19 anishcode19 changed the title Challenge (23/30) : anishcode19 Challenge (24/30) : anishcode19 Sep 24, 2022
@anishcode19
Copy link
Author

I explored many repository issues and commented on 1 -2 issues for approval or assignment. I will update my work.

@anishcode19
Copy link
Author

anishcode19 commented Sep 25, 2022

Challenge- 25

I have been assigned 2 issues and I have started working on them and will make a PR for them asap

That's it for today!!

@anishcode19 anishcode19 changed the title Challenge (24/30) : anishcode19 Challenge (25/30) : anishcode19 Sep 25, 2022
@anishcode19
Copy link
Author

anishcode19 commented Sep 26, 2022

Challenge- 26

I have registered for Hacktoberfest and
I got the Hacktoberfest 2022: Registered badge from Hacktoberfest!
https://www.holopin.io/claim/cl8j3tc30828609kzv27v472k

@anishcode19 anishcode19 changed the title Challenge (25/30) : anishcode19 Challenge (26/30) : anishcode19 Sep 26, 2022
@kuraakhilesh8230
Copy link

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

@anishcode19
Copy link
Author

Challenge 27

  • I already registered for Hacktoberfest
  • I am participating as a contributor and maintainer for this Hacktoberfest 2022.

Tips

  • For PRs to be counted into your participation in Hacktoberfest, they must be merged between October 1st and October 31st.
  • As a beginner, try contributing to documentation issues like updating links, renaming, etc. This will give you an idea about open source contribution, forking repo, Pull request, PR merge, etc.
  • We need to submit at least four PRs 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.
  • Contributions must be made to public repositories.

Some repositories for Contribution

@anishcode19 anishcode19 changed the title Challenge (26/30) : anishcode19 Challenge (27/30) : anishcode19 Sep 27, 2022
@anishcode19
Copy link
Author

anishcode19 commented Sep 28, 2022

Challenge 28

I have created a pull request for one of the issues that I was assigned.
I contributed to 1 good first contributions now:

One of my PRs got merged successfully into the project.
Also Reading some repository contribution guidelines.

Also, clone the repository of 60 seconds of code in C++ and trying to contribute more to this repo.

1

@anishcode19 anishcode19 changed the title Challenge (27/30) : anishcode19 Challenge (28/30) : anishcode19 Sep 29, 2022
@anishcode19
Copy link
Author

anishcode19 commented Sep 29, 2022

Challenge 29

Ideas that I liked :

  1. CSS Generator
  2. Real-time Chat App💌
  3. Real Time Code Plagiarism and Contestant Removal

29

My opened Discussion link -

Virtual Travel guide

day-29

@anishcode19 anishcode19 changed the title Challenge (28/30) : anishcode19 Challenge (29/30) : anishcode19 Sep 29, 2022
@anishcode19
Copy link
Author

Challange 30

Successfully completed all the challenges. Thanks to Scaler for organizing it, everyone in the community was helpful and encouraged a lot during these 30 days. It was a great learning experience with Scaler Open-Source. As I was a beginner to GitHub so I didn't have even the basic knowledge of using GitHub, but due to these challenges only I was able to learn and understand many new and important things.
Lastly, I will continue my journey of open source, really excited about Hactoberfest as this will be the first time I will participate.

@anishcode19 anishcode19 changed the title Challenge (29/30) : anishcode19 Challenge (30/30) : anishcode19 Sep 30, 2022
@Mrjoy832
Copy link

Milestone-4 done ✅

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants