Challenge Day 30/30- Prakash Gatiyala

[PrakashGatiyala]

name: Prakash Gatiyala github_user_name: PrakashGatiyala

[PrakashGatiyala]

• URL of forked repository: https://github.com/PrakashGatiyala/scaler-september-open-source-challenge
• A screenshot of the cloned project in system:

[PrakashGatiyala]

[PrakashGatiyala]

Updating main branch Updating PrakashGatiyala-details

[PrakashGatiyala]

Challenge 9: Before the removing the Challenge 8 commit(632c2c2df3e1c9fe1337565695ea2fc2aa94047c)

After the removing the Challenge 8 commit(632c2c2df3e1c9fe1337565695ea2fc2aa94047c)

Process:

[PrakashGatiyala]

Challenge 11:

[PrakashGatiyala]

Challenge 13: For untracked files :

For tracked files:

[PrakashGatiyala]

Challenge 14 Process for creating merge conflict

Process for resolving merge conflict

[PrakashGatiyala]

Challenge-16 : Conflict in pull request

Resolved this merge conflict using local git

Resolved the conflict in pull request

[PrakashGatiyala]

GitHub Desktop - Day 17 Downloaded GitHub desktop

Created a new repository on GitHub

Added my name in README file

Published the repo on remote:

Created the new Branch: Created new File Merging the main branch to new Branch Repo reflected on remote

PR created from new Branch to main:

Pull the remote changes by clicking on Pull Origin

• Very user friendly
• Can do almost everything: pull, push, create commit, create repo, create new branch, merge branch, revert commit and much more.

[PrakashGatiyala]

Challenge 18:

Link of software development related topic gist

https://gist.github.com/PrakashGatiyala/0a4b38b3c465fab417d0539ae2cde3b7

Link of code snippet in Java gist

https://gist.github.com/PrakashGatiyala/a82a52413bfa59a58dac409603335f7b

[PrakashGatiyala]

Challenge 19: Process:

Result: 😄

[PrakashGatiyala]

Challenge 20: Project board Link

Created a GitHub repository

Created a project board with a TODO column, In progress, Done and Created a card for all the items in the TODO column

Tasked moved In progress column

Done with the In progress task and moved the card to the Done column

[PrakashGatiyala]

Challenge 21 I've gone through the Git Alias documentation. Created 4 alias for git commands(checkout, branch, commit and status) Screenshot of the alias I've created

Screenshot of using these alias

Completed.

[kuraakhilesh8230]

Congrats you have successfully completed milestone 2 and you are good to move onto next milestone All the best✅️

[PrakashGatiyala]

Challenge-23 :

Git Branches Regular Git Branches

• Development (dev) is the main development branch
• Master (master) is the default branch available in the Git repository
• QA (QA), or test branch contains all the code for QA testing

Temporary Git Branches: these are the branches that can be created and deleted when needed

• Bug Fix
• Hot Fix
• Feature Branches
• Experimental Branches
• WIP branches

Git Branching Naming Convention

• Start branch name with a Group word : Bug and WIP
• Use Unique ID in branch names : Example-> wip-8712-add-testing-module
• Use Hyphen or Slash as Separators: Example-> feature_upgrade_jquery_version_login_module
• Git Branch with Author Name: Example-> PrakashGatiyala_feature_new-experimental-changes
• Avoid using numbers only
• Avoid using all naming convention simultaneously
• Avoid long descriptive names for long-lived branches

Pull Request

TIP 1: Give your feature branch a clear name TIP 2: Give your commits and PRs active and descriptive titles: use “Fix dashboard typo” instead of “Fixed” or “Fixes.” TIP 3: Streamline your process of creating a new PR TIP 4: Give your PR a meaningful description: Why? How? What? TIP 5: Show your functionality visually, whenever possible: Use gist TIP 6: Review your own PR before you assign it to others: resolve any conflicts , Run your tests! Lint your code!

CONTRIBUTION GUIDELINES FINDING AN ISSUE

• Issues available for community contribution: help wanted , good first issue
• Issues not available for community contribution: 🔒 staff only
• Issues not ready for work: 🚧 status: blocked, 🧹 status: ticket work required , 🚦 status: awaiting triage
• Issues without any of the above labels: Ask in comments

CONTRIBUTION PROCESS

1. Comment on it and say you're working on that issue.
2. Write your code and submit your pull request
3. Wait for code review

PROPOSING A NEW ISSUE

1. Create a new GitHub issue associated with the relevant repository
2. The issue will automatically have the 🚦 status: awaiting triage label applied.
3. Once the project maintainer has approved the issue and removed the 🚦 status: awaiting triage label, you may start work on code as described in the "Contribution process" section above.

[PrakashGatiyala]

Challenge 24:

I've found one issue of Hacktoberfest2022 Project

I've requested for myself to get assigned to it.

I've started working on it. PR Link: https://github.com/MrKrishnaAgarwal/Hacktoberfest2022/pull/36

PR is merged now. Issue is now completed.

I have been assigned 1 more issue. I'm working on it.

• https://github.com/MrKrishnaAgarwal/Hacktoberfest2022/issues/39

[PrakashGatiyala]

Day 25

I have been assigned 1 issue and I have started working upon them and will make a PR for it asap.

• https://github.com/MrKrishnaAgarwal/Hacktoberfest2022/issues/39

My OpenSource projects for beginner: https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems

I'm creating issue for my Open Source Project. Assigning issues to beginner enthusiast who are looking for beginner-friendly issues. Maintaining my Project and reviewing the code in PR. Helping beginners to create issues and make a PR.

Open an issue : https://github.com/OpenGenus/cosmos/issues/6410

waiting for getting assigned to it.

Created a Open source Project Repo with Scaler Discord Members.

60 seconds of code in C++

[PrakashGatiyala]

Challenge 26

• [X] Registration completed for https://hacktoberfest.com/.

PR for following issue is now merged

• https://github.com/MrKrishnaAgarwal/Hacktoberfest2022/issues/39

  

Reviewing the issues and PR for following Repo.

• 60 seconds of code in C++

• hackerrank_problems-or-hackerearth_problems

[PrakashGatiyala]

Challenge 27

• [X] I've gone through the rules and resources provided by Hacktoberfest

• [X] Explored different open source repositories and created an open source repository 60 seconds of code in C++ by collaborating with Scaler discord member.

• I want to work on issues related to C++, JavaScript code for Hacktoberfest (for example https://github.com/OpenGenus/cosmos repo.)

I am a maintainer and a contributor as well for this Hacktoberfest 2022.

I'm reviewing the issues and PR for my Repo hackerrank_problems-or-hackerearth_problems

My Tips

Best practices when participating in Hacktoberfest.

• Register anytime between September 26 and October 31
• Pull requests can be made in any GITHUB or GITLAB hosted project that’s participating in Hacktoberfest
• Have 4 pull/merge requests accepted between October 1 and October 31 to complete Hacktoberfest

RESOURCES FOR BEGINNERS

• DigitalOcean: INTRODUCTION TO GITHUB AND OPEN-SOURCE PROJECTS
• GitHub: HOW TO CONTRIBUTE TO OPEN SOURCE
• DigitalOcean: WHAT IS OPEN SOURCE
• DigitalOcean: HOW TO USE GIT

START CONTRIBUTING

• List of beginner repositories: UP-FOR-GRABS.NET
• GitHub repository: FIRST-CONTRIBUTIONS
• GitHub repository: AWESOME-FOR-BEGINNERS

PULL/MERGE REQUEST DETAILS

HERE’S HOW WE VALIDATE CONTRIBUTOR PULL/MERGE REQUESTS (“PR/MRS”) FOR HACKTOBERFEST

• your pr/mrs must be within the bounds of hacktoberfest.
• repos that go against hacktoberfest’s values will be excluded from qualification and pr/mrs made to those repos won’t count.
• your pr/mrs must not be spammy.
• your pr/mrs must be in a repo tagged with the “hacktoberfest” topic, or be labeled “hacktoberfest-accepted.”
• your pr/mrs must not be labeled as “invalid”.
• your pr/mrs must be merged, have the “hacktoberfest-accepted” label, or have an overall approving review.
• once your pr/mrs pass all the checks above, it will be accepted for hacktoberfest after the 7-day review period.

[DaltonDeven]

All Set To Go Verified for Milestone-3 Congrats👍

[PrakashGatiyala]

All Set To Go Verified for Milestone-3 Congrats👍

Thank You :)

[PrakashGatiyala]

Challenge 28

Current status of contributing to open source

Following are the Pull Requests created and successfully Merged:

• https://github.com/MrKrishnaAgarwal/Hacktoberfest2022/pull/36
• https://github.com/MrKrishnaAgarwal/Hacktoberfest2022/pull/55

These are the Issues created

• https://github.com/OpenGenus/cosmos/issues/6410

• 

Collaborated with rest of folks in the communtiy.

Opened a new open source repository exclusively for beginner 60 seconds of code in C++

Doing the Issue and PR reviews for my Repository.

[PrakashGatiyala]

Challenge 29

• [X] I've checkout the existing ideas other community members have already shared.

Following existing idea, I liked.

• https://github.com/scaleracademy/open-source-projects/discussions/63

Suggested a new feature for existing idea.
https://github.com/scaleracademy/open-source-projects/discussions/63#discussioncomment-3766088

• https://github.com/scaleracademy/open-source-projects/discussions/45

Suggestion for existing idea.
https://github.com/scaleracademy/open-source-projects/discussions/45#discussioncomment-3766159

My New project idea

https://github.com/scaleracademy/open-source-projects/discussions/138

[PrakashGatiyala]

Challenge 30

• [X] I've completed all the challenges.

Hacktoberfest

I'm excited about Hacktoberfest. I will kick start yet another open source journey with Hacktoberfest. I will try to contribute beyond the Hacktoberfest.

Experience of this initiative.

• [X] It was a great initiative. Special thanks to Scaler Team for organizing it for beginner.
• [X] I've learn lot of new things from this Open Source challenge. Like most common used cmds for git, github pages, github gist etc.

Thank you Scaler Discord Team.

[kuraakhilesh8230]

congrats you have completed milestone-4 successfully and you are good to go🎉