All Challenges : Mausoomi Roy

[Mausoomi12]

name: Mausoomi Roy
github_user_name: Mausoomi12
discord_id: mausoomi12

[Mausoomi12]

URL of forked repo : https://github.com/Mausoomi12/scaler-open-source-september-challenge
Screenshot :

[Mausoomi12]

Day 3:

Local system:

Github:

[Mausoomi12]

Day 4:

Local System:

Github:

[Mausoomi12]

Day 7:

Local System:

Github:
https://github.com/scaleracademy/scaler-open-source-september-challenge/pull/714/commits

[Mausoomi12]

Day 8:

Local System:

Created new branch and md file:

Pushed into new branch (challenge8):

Github:
https://github.com/Mausoomi12/scaler-open-source-september-challenge/blob/challenge8/contributors/shivaylamba/Mausoomi12/Mausoomi12-3.md

[Mausoomi12]

Day 9:

Local system:

Github:

[Mausoomi12]

Day 10:

Local System:

Github:

[Mausoomi12]

Day 11:

Using Stash command:

[Mausoomi12]

Day 12:

Local System:

GitHub:

Mausoomi12@b173e8f

[Mausoomi12]

Day 13:

Local System:

GitHub:

https://github.com/Mausoomi12/scaler-open-source-september-challenge/blob/Mausoomi12-details/contributors/Mausoomi12/gist-solutions.md

[Mausoomi12]

Day 14:

Local System:

Github:

https://github.com/Mausoomi12/scaler-open-source-september-challenge/blob/Mausoomi12-details/contributors/Mausoomi12/Mausoomi12.md

[Mausoomi12]

Day 15:

1. Made a new directory:
   
2. Initialized the directory:
   
3. Added content in master branch:
   
4. Added changes in feature-branch:
   
5. Created a merge conflict:
   
6. Resolved merge conflicts in the Merge Editor:
   

[Mausoomi12]

Day 16:

Local System:

1. Synced local repo with original repo:

2. Committed changes made in challengers-list.md:

Github:

challengers-list

[Mausoomi12]

Day 17:

PR before resolving the conflict:

Local system:

1. Pulled the changes from the original repo to the local repo and merged with Mausoomi12-details to show the conflict in my local system:

2. Made the appropriate edits in the Merge Editor:

3. Pushed the changes:

Github:

challengers-list.md

PR after resolving conflict:

[Mausoomi12]

Day 18:

GitHub Desktop:

1. Performed various operations like commit, push, branching, etc. and created & resolved a merge conflict:

2. Created 3 different branches:

EXPERIENCE:

It was a nice and refreshing experience to work in a new interface. However, I personally prefer to work with GIT CLI.

[Mausoomi12]

Day 19:

1. Creating codespace on main:

2. Committing changes with codespaces:

3. Commit is reflecting in GitHub repo:

EXPERIENCE:

GitHub Codespaces lets me code from anywhere, integrates seamlessly with Visual Studio Code, and simplifies environment setup. Collaborative coding is a breeze, but it relies on a stable internet connection. It's great for onboarding, code reviews, and experimentation in my workflow.

[Mausoomi12]

Day 20:

1. Setting up Workflow:

2. Added code in lint.yml :

3. Added hello.js :

4. Jobs:

Workflow pass ✅:

EXPERIENCE:

As a beginner, setting up GitHub Actions felt empowering and helped me catch errors early, and gain confidence in my code contributions.

[Mausoomi12]

Day 21:

1. Created a project board named TODO LIST:

2. Added tasks in Todo column:

3. Moved tasks to In Progress and Done Column:

[Mausoomi12]

Day 22:

1. Created and used 2 aliases:

2. List of aliases created:

[Mausoomi12]

Day 23:

1. Created and pushed the static website:

2. Deployed the website on GitHub Pages: Mausoomi-Portfolio

3. Added and pushed GitHub Pages link in Mausoomi12.md file:

[Mausoomi12]

Day 24:

1. Git Branching Naming Convention:

• Use Unique ID in branch names
• Use Hyphen or Slash as Separators
• Avoid using numbers only
• Avoid long descriptive names for long-lived branches

2. Pull Requests:

• Give your feature branch a clear name
• Give your commits and PRs active and descriptive titles
• Give your PR a meaningful description
• Review your own PR before you assign it to others

3. Issues:

• Never contribute to issues which have labels like: 🔒 staff only , 🚧 status: blocked or 🚦 status: awaiting triage.
• Create only meaningful issues
• Always see for good-first-issue in the repos

4. More GitHub best practices:

• Write clear and well-formatted README.md and documentation files
• Automate tasks like testing, building, and deploying your code using GitHub Actions workflows
• Include a .gitignore file
• Limit the number of collaborators with write access to your repositories
• Actively participate in code reviews for your own and others' PRs

[Mausoomi12]

Day 25:

1. Found a open-source repo to contribute through This website:

2. Went to the first good-first-issue listed below:

3. Asked for permission to contribute:

4. Contributed by making some changes in the forked repo:

5. Opened a Pull Request:

6. Now, waiting for review:

[Mausoomi12]

Day 26:

Still waiting for the review:

[Mausoomi12]

Day 27:

1. Created new branch 'branchA':

2. Made changes in the hello.js file in branchA:

3. Created another branch 'branchB':

4. Made some changes in the same file in branchB:

5. Identified the commit ID to cherry-pick:

6. Used the cherry-pick command:

7. Resolved conflicts in merge editor:

8. Pushed into remote repo:

[Mausoomi12]

Day 28:

1. Registered for Hacktoberfest:

2. Created a pull request and waiting for the review:

[Mausoomi12]

Day 29:

Here is my Readme.md:

[Mausoomi12]

Day 30:

Filled the google form:

Successfully completed the 30 day challenge!!