Challenge #1- #29,#30 Divya#0416

[Divya4879]

name: Divya github_user_name: Divya4879 discord_id: Divya#0416

[Divya4879]

Forked Repository Link - https://github.com/Divya4879/scaler-open-source-september-challenge.git

Screenshot of the cloned repo in my PC-

[Divya4879]

Screenshot showing the list of all the current branches inside of my forked clone repository

[Divya4879]

Screenshot showing the latest repository contents of my forked clone repository locally-

[Divya4879]

Challenge 5 done

[Divya4879]

challenge 6 done

[Divya4879]

Day 7 challenge done

[Divya4879]

Day 8 challenge - Today i updated main branch as per the challnge and created a new pull request to the https://github.com/scaleracademy/scaler-open-source-september-challenge repository, previously i was creating a pull request to my repo itself, but it was to different branches.

[Divya4879]

The 9th day challenge has been completed since the new squashed commit message is showing on my[forked remote repo- https://github.com/Divya4879/scaler-open-source-september-challenge/tree/challenge8

[Divya4879]

Screenshot of the terminal when I have successfully used the git rebase to squash the commits

[Divya4879]

Screenshot of Challenge 11-

[Divya4879]

DAY 12 TASK - USING GPG TO VERIFY COMMIT

Adding screenshot of the task-

[Divya4879]

Day 13 task

[Divya4879]

DAY 14 CHALLENGE - CHANGE Divya4879.md file in branch Divya4879-details, GIT REBASE COMMAND, AND SIGNING MY COMMIT

[Divya4879]

DAY 15 CHALLENGE- SCREENSHOTS OF TODAY'S CHALLENGE- CREATING MERGE CONFLICT, RESOLVING IT IN THE CODE EDITOR AND SHOWING SCREENSHOT OF MY TERMINAL

[Divya4879]

DAY 16 CHALLENGE - SYNC LOCAL REPO WITH MAIN REPO, ADD MY NAME TO THE FILE AND PUSH CHANGES , COMMITS MENTIONED IN PULL REQUEST

[Divya4879]

DAY 17 RESOLVE GIT MERGE CONFLICT BY EDITING challengers-list.md file

[Divya4879]

I am sharing screenshots of my experience using github desktop below :-

[Divya4879]

Day 19 done- I used the git repositiory created yesterday on github desktop- Screenshots-

I ADDED A FILE USING CODESPACE AND USED THE TERMINAL TO COMMIT, AND PUSH THE FILE TO MY REPOSITORY.

WHAT DID I LIKE ABOUT CODESPACE? I LIKE THAT IT'S A CLOUD BASED VERSION OF VS CODE EDITOR, WITH SOME PREINSTALLED FEATURES. I REALLY ENJOYED USING IT!

[Divya4879]

Day 20- created a new github repo and added 2 files - lint.yml and hello.py made some changes to the yaml file to run it successfully

sharing screenshots for today's task -

[Divya4879]

Screenshot showing my Github Project board, and the 3 columns

[Divya4879]

Screenshots of today's challenge using git alias

[Divya4879]

Screenshot of pull request -

screenshot of terminal

[Divya4879]

Summary of what I just learnt about what needs to be done for effective open source contribution, especially with respect to open source issue creation, best practices around branch/pull request creation:-

### Git Branches- Types and Conventions to be followed for naming them

1. Regular Branches : There should be 3 permanent base branches - master , dev and QA. The names signifies their purpose.
2. Start your branch name with a group word - your branch name should have the category/group tag you are working with. For example : while fixing a bug, the syntax should be --> group_tag-.
3. Using tracker ID in a branch would be ideal way to track the working tree .
4. Using of the / as separators increases the readability and avoid confusion.
5. You can add your name to the branch to signify your bug fixes. Note : avoid using long names , which might increase confusion". Pull Request

Building a Great PR(Pull Request)

1. Give your PRs descriptive title to make other easy to track your working tree.
2. Streamline your process of creating a new PR.
3. PR should gave some meaningful descriptions as it reduces time and complexity of your work and also decrease confusion.
4. Show your functionality visually, whenever possible.

### Issues

1. If you are a beginner start with a good-first-issue issue tag.
2. If you want to work on a issue, then comment on that "you want to work on that issue".Wait for the review and check for another issue as soon as possible.
3. Create a GitHub issue with the relevant repository and propose your change there.

Note : Make sure that you proposed a relevant issue on your repository.

To understand more on these topics, i am attaching video for all in one guide to all these topics- https://www.youtube.com/watch?v=8wt-8B9vCQg

[Divya4879]

Day 25 task-

I checked out some projects and their "'good first issues". I feel that even though I can solve some of them with my current skills, I still need to spend much more time reading the documentation if the project to understand where and how to put my code to PR to possibly solve the issue.

Today i didn't find an issue i will be working on, but it was the 1st time I explored the open-source projects and went through the good 1st issue'd tagged issues.

I will be exploring more to contribute where I can. In the journey of open source, I am at the stage of exploring issues to solve in others projects.

Thank you for this opportunity.

[Divya4879]

Day 26 tasks :-

1. Today I explored more good-first-issue PROJECTS and made a list of them.
2. Read different CONTRIBUTING.MD files and also brushed up more GitHub commands and concepts.
3. Collected some of the active repositories which accept open source contribution.
4. Sent messages to a few to ask if the issue is still unsolved and if I can work on them.
5. Working on some tech stacks to make an open source project of my own.

[Divya4879]

Screenshots of cloning my repo, creating branches A and B, commits on branch A and cherry-picking 2nd commit to branch B -my local terminal(Git Bash) , and my github online/remote pushed updates and commits

![Uploading Screenshot (1841).png…]() ![Screenshot (1842)](https://github.com/scaleracademy/scaler-open-source-september-challenge/assets/86043076/b734cabd-28a7-4a9c-82f0-e7b04b3490b3

[Divya4879]

DAY 28 CHALLENGE -

1)I have been exploring many open-source projects since day 25, and have found a project repo with an easy contibution. I pulled my PR yesterday, and it has been merged into the main repo yesterday as well.

2) I am sharing my merged repo, their repo and the screenshots-

my merged repo- https://github.com/hellofaizan/xprofile/pull/96#event-10484272769

repository link - https://github.com/hellofaizan/xprofile

screenshots -

[Divya4879]

Today I created my Github profile Readme as part of the 29th Day challenge. My profile link is - https://github.com/Divya4879

[Divya4879]

Day 30 Challenge- Submitted the form I have completed all the days' challenges this month, so no task for today