Challenger - Hemant - Hemxnt21

[Hemxnt]

Name: Hemant Singh
github_user_name: Hemxnt
discord_id: 927096347495104533

[Hemxnt]

Challenge #2

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

[Hemxnt]

Challenge 3

[Hemxnt]

Challenge 4

[Hemxnt]

Challenge #5

update your forked repository and then create a Pull Request

#932 (comment)

[Hemxnt]

Challenge #6

#932 (comment)

[Hemxnt]

Challenge #7

[Hemxnt]

Challenge #8

1. Created a new branch in the local repo named challenge8.
   

2. Added a new file in contributors/Hemxnt named Hemxnt3.md and added some random text in it.
   

3. Pushed this new branch on my forked remote repo.
   

[Hemxnt]

Challenge - 9

[Hemxnt]

Challenge 10

[Hemxnt]

Challenge 11

[Hemxnt]

Challenge 12

[Hemxnt]

Challenge 13

[Hemxnt]

Challenge 14

[Hemxnt]

Challenge 15

[Hemxnt]

Challenge 16

[Hemxnt]

Challenge 17

[Hemxnt]

Challenge 18

[Hemxnt]

Challenge 19

[Hemxnt]

Challenge 20

[Hemxnt]

Challenge 21

[Hemxnt]

Challenge 22

[Hemxnt]

Challenge 23

[Hemxnt]

Challenge 24

PR

Give your feature branch a clear name
Give your commits and PRs active and descriptive titles
Show your functionality visually (gifs,img,etc)

Issues

Issues available for community contribution:
help wanted
good first issue

Issues not available/ready for community contribution:
🔒 staff only
🚧 status: blocked
🧹 status: ticket work required
🚦 status: awaiting triage

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.

Branch(s)

Two Categories -
Regular branchs (Parmanent) -

1- dev Branch
Development (dev) is the main development branch. The dev branch’s idea is to make changes in it and restrict the developers from making any changes in the master branch directly.
2- master Branch
Master (master) is the default branch available in the Git repository. It should be stable all the time and won’t allow any direct check-in.
3-QA or test branch
QA (QA), or test branch, contains all the code for QA testing and automation testing of all changes implemented. Before any change goes to the production environment, it must undergo the QA testing to get a stable codebase.

Temporary branchs -
Bug Fix
Hot Fix
Feature Branches
Experimental Branches
WIP branches (work in progress)

Naming Convention -

1- Start branch name with a Group word
bug-logo-alignment-issue
wip-ioc-container-added

2- Use Unique ID in branch names
wip-8712-add-testing-module

3- Use Hyphen or Slash as Separators
feature_upgrade_jquery_version_login_module

4- Git Branch with Author Name
format - <author>_<branch-type>_<branch-name>
E.g., rajeev.bera_feature_new-experimental-changes

5- Avoid using numbers only

6- Avoid using all naming convention simultaneously

7- Avoid long descriptive names for long-lived branches

Extra n Imp (OpenSource Best Practices)

Be Polite
Use a Unique Repository for Each Project.
Always Update Your Branches i.e. Sync your branches and Forks.
Always Use an Authorized Email to Commit Code and with Sign-off.
Create a Meaningful .gitignore File.
Do not push to main or master branch directly.

[Hemxnt]

Challenge 25

I've recently embarked on my journey to explore open source projects, both on https://goodfirstissue.dev/ and GitHub. As of now, I'm still in the process of discovering suitable issues to contribute to. I'm actively engaging with various projects and eagerly searching for opportunities to make meaningful contributions. 🌱🚀

[Hemxnt]

Challenge 26

Found an repo to contribute.
Link of the Repo: https://github.com/arguflow/arguflow
PR Link: devflowinc/trieve#536 (comment)

Got an issue and going to fix it in meanwhile ...

[Hemxnt]

Challenge 27

[Hemxnt]

Challenge 28

Looking for more open source project to contribute.

and now going to land on Hacktoberfest

[Hemxnt]

Challenge 29

Registered for Scaler OpenQuest hackathon and looking for team mates . <3

Github profile

[Hemxnt]

CHALLENGE COMPLETED

Completing the Scaler Open Source September Challenge was a wild ride! 🎢 I faced countless challenges, got stuck a bunch of times, but you know what? I learned so much along the way. 🚀

This journey not only helped me crush it at Hacktoberfest but also set me up for success in GSoC. 💪 The research I did? Priceless. 🤓 Shoutout to the awesome Discord community that had my back whenever I needed help. 🙌

Big thanks to @shivaylamba and everyone at #OpenSourceSeptemberChallenge . 🙏 What an incredible journey! 🌟