Challenger Mathankumar-P

[Mathankumar-P]

Challenge#1 :

Name: Mathankumrar P Github : Mathankumar-P (https://github.com/Mathankumar-P) Discord : Mathankumar#6839 [Mathankumar45]

[Mathankumar-P]

Challenge#2 : Fork and clone the repository

Link to forked repo : https://github.com/Mathankumar-P/scaler-open-source-september-challenge PC Screen Shot

[Mathankumar-P]

Challenge#3 Create a branch "Mathankumar-P-details"

completed

[Mathankumar-P]

Challenge#4 => Sync with Original Repo & add upstream branch

Completed

git repo link : https://github.com/Mathankumar-P/scaler-open-source-september-challenge

[Mathankumar-P]

Challenge#7 => git reset & git push force

before reset

before reset -> console head_id

After reset

force pushed the branch to pull request

[Mathankumar-P]

Challenge-8

Create a new branch named challenge8 and add a new .md file, learn about rebase, squash, merge

[Mathankumar-P]

Challenge 9 : Rebase & Squash attached before after images

before rebase [newly added =>commit-3 rebase / rebase feautre 2]

After rebase => merged above mentioned 2 commit to commit new changes for rebase

[Mathankumar-P]

Challenge#11 Stash and remove stash => Completed

[Mathankumar-P]

Challenge 16 - add your name to contributors to resolve conflict

[Mathankumar-P]

Challenge-17 Resolved conflict

[Mathankumar-P]

Challenge18-Completed

[Mathankumar-P]

Challenge-19 - Using Code Spaces

I greatly appreciated its concept of offering online resources that enable you to connect or code from any location using any available device.

A few aspects of Codespace that particularly appealed to me include its Instant Development Environment, seamless Version Control Integration, Collaboration capabilities, and the availability of Pre-Configured environments, among other features.

[Mathankumar-P]

Challenge-20

Created lint code file but will fix them

[Mathankumar-P]

Challenge-21 - Setup kanban board

[Mathankumar-P]

Challenge-22 Use Git Hub Alias.

[Mathankumar-P]

Challenge-23 - github pages

https://mathankumar-p.github.io/GitHubPages/

[Mathankumar-P]

Challenge-24

Git Branching Naming Convention: Best Practices Takeaways:

• Branches in Git can be categorized into regular and temporary types.
• Regular branches like dev, master, and QA are permanent, while temporary ones, like bug fix, hotfix, feature, experimental, and WIP, are created and removed as needed.
• The key to Git branching naming conventions is consistency and informativeness.
• Best practices for naming branches include starting with a descriptive word like bug, wip, or feature, incorporating a unique identifier like the issue tracker ID, using hyphens or slashes as separators, optionally including the author's name, avoiding numeric-only names, refraining from mixing different naming conventions, and keeping long-lived branch names concise.

Best Practices for Creating a Great Pull Request:

• For feature branches, employ clear names, possibly prefaced with your initials in multi-contributor projects.
• Craft commits and pull request titles that are active and descriptive, using the present imperative tense.
• Simplify PR creation using a bash function or the hub command.
• Provide a meaningful PR description that delves into the why, how, and what of your changes.
• Whenever possible, illustrate your changes visually through screenshots, animated GIFs, or screen recordings.
• Before assigning your PR to others, carry out a self-review that includes catching up with recent changes, resolving conflicts, running tests, code linting, and verifying your alterations.

Contributing Guidelines Highlights:

• Seek issues marked as "help wanted" or "good first issue" to contribute to.
• Notify others by commenting on the issue to avoid conflicts.
• Develop your code and submit a pull request, adhering to the provided guidelines.
• Be patient during the code review process and address any raised issues.
• Foster collaboration by reviewing fellow contributors' pull requests and providing constructive feedback.
• If you wish to work on an unaddressed issue, create a new issue with your proposed changes and await project maintainer evaluation. Once approved, commence work on the code.

[Mathankumar-P]

Challenge-25

Finding a good open-source project is difficult. as a java backend developer struggling to find a project to contribute. Most of the good first issues are either commented or work in progress. hoping to find a good project in the near features. scaler's discord guidance will be really appreciated in getting started with the open source.

[Mathankumar-P]

Day-26

Overlooked a few repositories and tried to understand the issues. couldn't find any beginner-friendly in those. also hope that I will find the repo for open source.

Most of the repository which was mentioned in many Good first issue are either inactive or i am not able to get the hang of it

looking for java related repo's.

[Mathankumar-P]

Challenge-27 - Using cherry pick comment

[Mathankumar-P]

Day-28

Hustling to find a project. will find them soon.

[Mathankumar-P]

Challenge-29 - Create readme profile;

GIt hub readme link : https://github.com/Mathankumar-P/Mathankumar-P