#Challenge_1

[Mahesh0911]

name: Mahesh Dudhe github_user_name: Mahesh0911 discord_id: Maheshrd#6659

[Mahesh0911]

URL of forked repository : https://github.com/Mahesh0911/scaler-open-source-september-challenge Screenshot of the cloned repo in system/PC :

[Mahesh0911]

URL of the forked repository : https://github.com/Mahesh0911/scaler-open-source-september-challenge/tree/Mahesh0911-details

[Mahesh0911]

[Mahesh0911]

Task of Day #5 :

[Mahesh0911]

Day #6 :

[Mahesh0911]

Task of Day #7 : The concept of Git Reset

[Mahesh0911]

Challenge #9 : Concepts of Git Rebase and Git Squash

[Mahesh0911]

Challenge #10 : Git Rebase on a Pull Request.

[Mahesh0911]

Using stash commands in Git challenge #11:

[Mahesh0911]

Challenge #12 : Added signed commit

[Mahesh0911]

Challenge #13 : gist solutions

[Mahesh0911]

Challenge #14 : Re-practice of the 8th and 9th Challenge

[Mahesh0911]

Challenge #15 : Resolving merge conflicts

[Mahesh0911]

Challenge #16 : Resolving merge conflicts via git

[Mahesh0911]

Challenge #17 : Fix merge conflicts via git

[Mahesh0911]

Challenge #18 : Github Desktop

[Mahesh0911]

Challenge #19 : Codespaces GitHub Codespaces streamlines collaborative development. Instant environment setup. Integration with repositories is seamless. Customization takes time. Useful for onboarding and reproducible environments.

[Mahesh0911]

Challenge #20 : Github Actions

[Mahesh0911]

Challenge #21 : Project Boards on GitHub

[Mahesh0911]

Challenge #22 : Git Aliases

[Mahesh0911]

Challenge #23 : Github Pages

[Mahesh0911]

Challenge #24 : Git Branching Naming Convention:

1. Start branch name with a Group word
2. Use Unique ID in branch names
3. Use Hyphen or Slash as Separators
4. Git Branch with Author Name
5. Avoid using numbers only
6. Avoid using all naming convention simultaneously
7. Avoid long descriptive names for long-lived branches

Building a Great Pull Request: TIP 1: Give your feature branch a clear name TIP 2: Give your commits and PRs active and descriptive titles TIP 3: Streamline your process of creating a new PR TIP 4: Give your PR a meaningful description TIP 5: Show your functionality visually, whenever possible TIP 6: Review your own PR before you assign it to others

CONTRIBUTION PROCESS Steps to make your contribution:

1. Comment on it and say you're working on that issue.
2. This is to avoid conflicts with others also working on the issue.
3. If you've followed the guidelines above, you don't need to ask permission to start work on an issue.
4. Write your code and submit your pull request.
5. Be sure to read and follow our pull request guidelines!
6. Wait for code review and address any issues raised as soon as you can.

[Mahesh0911]

Challenge #25 : Open Source Contribution I wanted to provide an update on my progress in today's challenge. I've been actively exploring various open source projects and getting familiar with their repositories and documentation. While I haven't yet found a specific issue to work on, I'm taking this time to gain a deeper understanding of the projects and their workflows.

I believe that this exploratory phase is crucial in preparing me for meaningful contributions in the future. I'm carefully reviewing project documentation, community guidelines, and engaging with the community to learn more.

I want to emphasize that I'm committed to contributing to open source, and I understand that it's a learning journey that requires patience and dedication. I'm excited about the opportunities that lie ahead and am looking forward to taking on my first task when the time is right.

[Mahesh0911]

Challenge #26 : Continuation of challenge 25 I'm providing an update on my progress for the open source contribution task, which is now on its second day.

Yesterday, I spent time exploring several open source projects that piqued my interest. I've been reading through project documentation, including README and CONTRIBUTING.md files, to understand the project's goals, codebase, and contribution guidelines. This initial exploration has been valuable in getting a sense of the projects and their communities.

However, as of today, I'm still in the process of identifying the perfect first issue to tackle. I want to ensure that my first contribution is well-aligned with my skills and the project's needs. I've continued to check for issues labeled as "good first issue" and have been engaging with the project communities through their communication channels to seek guidance and mentorship.

I want to reiterate my commitment to this journey of contributing to open source, even though finding the right starting point may take some time. Open source contributions are a learning process, and I'm dedicated to making meaningful contributions when the opportunity arises.

[Mahesh0911]

Challenge #27 : git cherry-pick cmd

[Mahesh0911]

Challenge #28 Update: Requested assignment for the 'arrays disjoint' issue in open source project. Excited to contribute.

[Mahesh0911]

Challenge #30: My Scaler Open-Source September journey has been rewarding. I've gained valuable Git and GitHub skills, thanks to the well-structured program and supportive community. Excited to apply these skills in my projects! I am excited to participate in more such challenges for learning and growing my knowledge.