Challenge #1 - Avesh Singh

[aveshCS]

name: Avesh Singh github_user_name: aveshCS discord_id: AveshCS#1950

[aveshCS]

Challenge 2: Create a fork of the repo and clone it [Status: Completed]

Repo link: https://github.com/aveshCS/scaler-open-source-september-challenge.git

[aveshCS]

Challenge 3 : Create a branch to the cloned repository [Status : Completed]

[aveshCS]

Challenge 4: Create an upstream and sync the local repo [Status: Completed]

[aveshCS]

Challenge 5 : Update contributors folder [Status : Updated]

[aveshCS]

Challenge 6: Update aveshCS.md file with github issue link [Status: Completed]

[aveshCS]

Challege 7 : Learn the use of git reset command [Status: Completed]

[aveshCS]

Challenge8: Learn about git rebase & git squash and create a new contributor file in a newly created branch. [Status: Completed].

[aveshCS]

challenge9: Use git rebase [Status : Completed]

[aveshCS]

Challenge10: Squash commit in branch [status: completed]

[aveshCS]

Challenge 11 : Learn git stash command , how to stash and clear the stash [Status : Complete]

[aveshCS]

Challenge 12 : Make signed commit [ Status : Completed]

[aveshCS]

Challenge 13 : Make gists and update aveshCS-details [Status : Completed]

[aveshCS]

Challenge 14 : Revise git rebase, squash and do a signed comment [Status : Done]

[aveshCS]

Challenge 15 : Learn to solve merge conflicts [Status : Completed]

[aveshCS]

Challenge 16 : Learn to emulate merge conflicts [Status : Completed]

[aveshCS]

Challenge 17 : Solve merge conflicts [ Status : Completed]

[aveshCS]

Challenge 18 : Learn to use github desktop [Status : Completed]

[aveshCS]

Challenge 19 : Learnt how to use github codespace [ Status : Completed] Pros : Loved the environment offered, very similar to vs code, that's why no hassle to migrate.

[aveshCS]

Challenge 20 : Learnt how to use github actions [Status : Completed] Learnt about a code linting. Lint is the computer science term for a static code analysis tool used to flag programming errors, bugs, stylistic errors and suspicious constructs.

[aveshCS]

Challenge 21 : Learnt how to use github project boards [ Status : Completed]

[aveshCS]

Challenge 22 : Learn git aliases [ Status : Completed]

[aveshCS]

Challenge 23 : Learn github pages [Status : Completed]

[aveshCS]

Challenge 24 : Summarize all four articles [ Contribution convention] mentioned in challenge 24 [Status : Completed]

Git branching naming conventions

We can divide Git branches into two categories

1. Regular Branches: Permanent branches in repository

   • Dev: Used for making changes in the code
   • OA: Used for all automation testing
   • Master: Default Branch

2. Temporary Branches: To be deleted when needed

   • Bug fix
   • Hot fix
   • Feature Branch
   • Experimental Branch
   • WIP(Work in progress) branch

Conventions

• Start branch name with group word like WIP, feature, etc
• Use unique id in names if there any, like bug id
• Use hyphen or slash as seprator between words for better readibility
• You can add author name to branch
• Avoid long names for permanent branch
• Avoid using every convention together

Building a great PR

• Well Named feature branch
• Write appropriate commit messages and pr descriptions.
• Describe your work properly in your PR
• Add visual representation whenever possible for better understanding
• Review your pr Yourself then assign it to others

Contributing Code

Find issues available for contribution by community

• Look for issues with tag 'help wanted' or 'good first issue', these issues are meant for community contributions.
• Issues with tag 'staff only' are not meant for community, ignore.
• Issues with tags ' status: blocked', ' status: awaiting triage' and 'status: ticket work required' are also not meant for community.

Contribution Process:

Once you have chosen the issue to work on, do the following:

• Comment on the issue that you are working on it
• Write code and submit PR, following all the pr guidelines
• Wait for feedback and collaborate accordingly.

Creating a new Issue:

If you cannot find an issue you want to work on in the issue section, create your new issue and wait for feedback.

[aveshCS]

Challenge 25: Explore github and find some good projects to contribute to. [Status : Ongoing].

Today's progress: Searched for projects utilizing JavaScript. Found few good first issue, but had no idea about the solution. Still looking for opportunity to contribute.

[aveshCS]

Challenge 26: Explore github and find some good projects to contribute to. [Status : Ongoing].

Today's progress: Still searching for good first issue.

[aveshCS]

Challenge 27 : Learn git cherry-pick command [Status : Completed]

[aveshCS]

Challenge 28 : Search for some open source project. [Status : ongoing] While exploring many open source projects I came across trafficserver project, today spent some time reading about the documentation of this project.

Today I registered for hacktober fest.

[aveshCS]

Challenge 29 : Customize github readme [Status : Completed]

[aveshCS]

Challenge 30 : Fill the form of milestone 4 [ Status : Completed] Loved the challenges so far, got to learn a lot.