Challenge 1 - Arijit Ghosh

[Rancho2002]

name: Arijit Ghosh github_user_name: Rancho2002 discord_id: arijitghosh

[Rancho2002]

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

[Rancho2002]

List of all the current branches inside my forked clone repository SS1 SS2

[Rancho2002]

The latest repository contents of my forked clone repository locally

[Rancho2002]

Challenge 7 - Use of git reset screenshot

Command SS

Github SS

[Rancho2002]

Challenge 8: Created challenge8 branch and pushed a sample file screenshot

[Rancho2002]

Challenge 9 : Intro to git rebase

Step 1: push some changes to fork repo

Step 2: checking commit ID via git log to identify which commit to rebase

Step 3: use pick for the commit ID that need to be taken to rebase and squash for the commit ID that message need to be edited

Step 4: using interactive rebase command via git rebase -i

Step 5: giving a new commit message

Step 6: force push to forked repo

Step 7: commit message edited successfully

[k0msenapati]

Awesome explanation

[Rancho2002]

Challenge 10

Checkout to challenge 3 branch and pushed changes

Checking logs and picking up the last commit to rebase

Used rebase -i and force pushed

reflection in github

[Rancho2002]

Challenge 11: Git Stash ( create and drop )

[Rancho2002]

Challenge 12: Making signed commit

Making a gpg keys

Setting up the configuration

Creating the public key to set GPG key in github

Creating a new signed commit and pushed

The commit is now verified

[Rancho2002]

Challenge 13

Created gists

Gists link added inside `github-username.md` directory

[Rancho2002]

Challenge 14: Revision of git rebase with signed commit and DCO check in PR

Rebasing in latest commit but has some merge conflicts

Fixing up conflicts and force pushed

Fixed the DCO check error

Finally verified PR with DCO check

[Rancho2002]

Challenge 15: resolve merge conflict

Creating conflict

• In git terminal

• Inside the text editor

Resolving conflict

Final commit

[Rancho2002]

Challenge 16: Emulate merge conflict

Screenshot of the updated challengers-list.md file in my forked repository

[Rancho2002]

Challenge 17 : Resolving conflict

• Updating the local files with conflicted files

• Resolving the conflict

• Commited the changes

• Fixed conflict

[Rancho2002]

Challenge 18: Intro to Github Desktop

• Creating a repo, updating the repo in github desktop and commit changes

• Pushing the code into origin (github) using github desktop

[Rancho2002]

Challenge 19: Intro to GitHub Codespace

• Created a new branch, make a code edit, and commit the change and pushed the changes from within Codespace

• Changes showcase in GitHub repository

Experience:

Github Codespace is not that helpful for me, because if any changes I need to do I just use the web editor and made the commit from the editor itself. So have not found anything unique in codespaces

[Rancho2002]

Challenge 20: Set Up a GitHub Action for Code Linting

[Rancho2002]

Challenge 21: Intro to projects in Github

[Rancho2002]

Challenge 22: Intro to Git Alias

• Setting up the alias command and if wrong unset

• List of all the alias using git config --get-regexp alias or cat ~/.gitconfig command

• Uses of git alias

[Rancho2002]

Challenge 23: Intro to Github Pages

• Made this site: https://rancho2002.github.io/scaler-action/

• Create the pull request as mentioned in the challenge23.md

• Pull Request link: https://github.com/scaleracademy/scaler-open-source-september-challenge/pull/584

[Rancho2002]

Challenge 24: How to properly do open source contribution

• We must have to give our branch a proper name

Regular Branches:

Basically 3 permanent base branches: master, dev, and QA, each has it specific purpose.

• Branch Naming:

Start branch names with a category or group tag relevant to work. For bug fixes, use the syntax: group_tag-<your_branchName>. Tracking ID should also be added Use "/" or "-" as separators in branch names for readability Optionally, add your name to the branch to signify ownership of bug fixes. Avoid overly long branch names to prevent confusion.

Pull Requests:

• Descriptive Titles:

PRs must have clear and descriptive titles to help others easily understand the changes.

• Streamline PR Creation:

Must practice a well-defined process for creating new PRs to ensure consistency.

• Meaningful Descriptions:

Include meaningful descriptions in your PRs to reduce complexity, save time, and minimize confusion. If possible, visually demonstrate the functionality or changes made in the PR. Issues:

Good-First-Issue:

If you're a beginner, start by looking for issues tagged as "good-first-issue" to get started.

Claiming Issues:

When you want to work on a specific issue, comment on it, expressing your intention to work on it. Wait for a review, but don't wait too long. If there's no response, consider moving on to another issue. Creating Issues:

If you have a new idea or want to address a problem, create a GitHub issue in the relevant repository. Make sure your proposed issue is relevant to the repository's purpose and aligns with its goals. By following these practices, you can contribute effectively to open-source projects, maintain a clear and organized development workflow, and collaborate smoothly with other contributors.

[Rancho2002]

Challenge 25

Looking for new issues still. But have checked out goodfirstissue site, and there are plenty of projects. Need to explore more.

[Rancho2002]

Challenge 26

• Registered for Scalar Open Quest Hackathon
• Created issue and assigned to me, and created a PR and make it merge (repo link: Here)

Assigning Issue

Make it merge

[Rancho2002]

Challenge 27

• Cloned repo

• Created branches and added commits

• Selecting this commit to be cherry picked

• Made some other commits too

• Switched to branchA and cherry picked specific commits

• Finally verifying which one applied on which branch

[Rancho2002]

Challenge 28

• Already made contributions and shared those with others in the Discord

• Registered for hacktoberfest

[Rancho2002]

Challenge 29

• Decorated my github readme file

[Rancho2002]

Challenge 30

I have successfully completed the open source September challenge for consistently 30 days. It's a really fun journey and my recommendation to others is to participate in open source activities because it gives you wide variety of learnings new things.