Challenge Submissions : Arup Bhowmick

[0xStryK3R]

name: Arup Bhowmick
github_user_name: 0xStryK3R

[0xStryK3R]

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

[0xStryK3R]

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

[0xStryK3R]

• Screenshot showing the latest repository contents

• Main Branch Updated
  

• Personal Branch Updated
  

• Local Repo Updated
  

[0xStryK3R]

Challenge 9 Tasks:

• Identify the commit id that needs to be removed (you should have created this in the 8th Challenge)
  

• Use git reset and force push, to remove the commit from your pull request.
  

• Share a screenshot of this, in the issue you created in previous challenges. Challenges - Arup Bhowmick #902
  

[0xStryK3R]

• Challenge 10 Task Completed
• Milestone 1 (Day 10) Reached
• Twitter Post Link

[0xStryK3R]

Challenge 11 Tasks:

• Create another branch from your current branch created in previous challenges (Don't create a new branch from main).
• Share screenshot of this new branch in the issue created in previous challenge

[0xStryK3R]

Challenge 13 Tasks:

• Inside the branch you created in the previous challenge your-username-details create a new file inside the contributors/<YOUR-GITHUB_USERNAME>/ directory.
• Use the git stash command to move these changes to the stash area
• Delete the content from the stash area and share a screenshot of this inside the Github issue you created in the first challenge

[0xStryK3R]

Challenge 14 Tasks:

• Follow the article shared above and try to reproduce a case of merge conflict in your system for a project and try to resolve it
• Share appropriate screenshot in the issue created in the first challenge.

[DaltonDeven]

Good to go verified ✅

[0xStryK3R]

Challenge 15 Tasks:

• Update your Forked Repo From the Original Repo. Also ensure that your branch your-user-name-details is also synced with the latest changes from the original repository

• In your branch your-user-name-details open the add your name to the list of challengers inside the challengers-list.md file by following the format in the file.

• Push your change to reflect in the Pull Request created in previous challenges.

• Challenges - Arup Bhowmick #902

[0xStryK3R]

Challenge 16 Tasks:

• You will notice that your pull request will have a conflict: image

• Try to resolve this merge conflict using local git

• Once resolved, share screenshot on the github issue created in the previous challenges

• Challenges - Arup Bhowmick #902

[0xStryK3R]

Challenge 17 Tasks:

• Download GitHub desktop
  

• Create a new repository on GitHub
  

• Add anything you want to your repo
  

• Follow through all the GitHub workflow you know using the GUI (commit, branching, pulling, pushing etc)

  • Publish Repo to Github Repo Link
    
  • Commit Changes to README.md
    
  • Push main branch to Origin
    
  • Create New Branch (test-branch)
    
  • Committed New Changes from test-branch
    
  • Published test-branch
    

• Share a screenshot of your experience using github desktop on the issue created in prior challenges
  

[0xStryK3R]

Challenge 19 Tasks:

• Create a new file inside your branch created in previous challenges your-username-details under the directory contributors/username. The file needs to be a source code file written in your preferred programming language. The code can be anything you want: hello world program or your favorite program.

• Commit the change and push it.

• Check if your linting fails in side the Pull request: passed

• Challenges - Arup Bhowmick #902

[0xStryK3R]

Challenge 20 Tasks:

• Create a GitHub repository for any project you can think up: Repo Link
• On a sheet of paper create a TODO list (or backlog) of features you want to have in you app
• Create a project board with a TODO column, In progress, Done Project Board
• Create a card for all the items you already wrote on the sheet of paper in the TODO column
• Work on the features synchronously and move the card respectively for each in progress task to the In progress column
• When you're done with the In progress task move the card to the Done column

Submission:

• Take a screenshot of your project board for when you moved an card from In progress to Done
• Add you screenshot to the Github issue created in the previous challenges

Board View:

Table View:

Working Project Snippets:

[0xStryK3R]

Challenge 21 Tasks:

• Go through the Git Alias documentation shared here

• Create at least 2 alias for any git commands you feel is too long
  

• Take a screenshot of the alias you created. hint run git config --list
  

• Take a screenshot of using your alias
  
  

• Post these screenshot in the issue created in the prior challenges

[kuraakhilesh8230]

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

[0xStryK3R]

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

Thankyou!! ☺️

[0xStryK3R]

Challenge 23 Submission:

Git Branches

Branch Categories

• Regular Git Branches: Development (dev), Master (master) and QA (QA)
• Temporary Git Branches: Bug Fix, Hot Fix, Feature Branches, Experimental Branches and WIP branches

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.

Pull Requests

Useful Tips

1. Give your feature branch a clear name.

   A well-formed PR should start with a well-named feature branch.

2. Give your commits and PRs active and descriptive titles.

   For both commit messages and PR titles, it's a good idea to use the present imperative tense — for example, use “Fix dashboard typo” instead of “Fixed” or “Fixes.”

3. Streamline your process of creating a new PR.

4. Give your PR a meaningful description

   A PR description section is where you let the reviewer know why you opened the pull request; the more information you give them before they look at your actual code, the easier their job will be.
   A basic description usually has these elements: Why How and What

5. Show your functionality visually, whenever possible

6. Review your own PR before you assign it to others

   • Make sure you are caught up with the latest changes in the develop branch; resolve any conflicts that might exist, so that merging is as easy as pressing a button.
   • Run your tests!
   • Lint your code!

Contributing Guidelines

Finding an Issue to Work On:

• Issues available for community contribution:
  • help wanted: Open to participation from the community but not necessarily beginner-friendly
  • good first issue: Open to participation from the community and friendly towards new contributors
• Issues not available for community contribution:
  • 🔒 staff only: Requires infrastructure access or institutional knowledge that would be impractical to provide to the community
• Issues not ready for work:
  • 🚧 status: blocked: Blocked by other work that needs to be done first
  • 🧹 status: ticket work required: Needs additional work before it is ready to be taken up
  • 🚦 status: awaiting triage: Has not been triaged by a maintainer
• Issues without any of the above labels.

Contribution Process

1. Identify issue to work on basis on above guidelines, and comment on it to avoid conflicts.
2. Write code and submit PR. PR should follow guidleines.
3. Wait for code review and address any issues raised as soon as you can.

Submitting a New Issue

1. Create a new GitHub issue associated with the relevant repository and propose your change there.
2. Wait for a project maintainer to evaluate your issue and decide whether it's something that we will accept a pull request for.
3. Once the project maintainer has approved the issue (by removing the 🚦 status: awaiting triage label), start work on code as described in above section.

[0xStryK3R]

Challenge 24 Update:

• I have requested to be added as contributor for the project deep-translator.
• They are looking to build website/api for the deep-translator package. I have requested to contribute for the same.

[0xStryK3R]

Challenge 24 Update:

• I have requested to be added as contributor for the project deep-translator.
• They are looking to build website/api for the deep-translator package. I have requested to contribute for the same.

Challenge 25 Update:

• No update received on the previous request submitted yesterday. Awaiting response from owner.
• Also looking for any other Open source repos I can contribute in as per my skillset - in case above one doesn't pan out. Haven't found anything else yet.

[0xStryK3R]

Challenge 26 Tasks:

• Do register today for https://hacktoberfest.com/
• Help out other folks, collaborate with each other as well for contributing to open source projects

[0xStryK3R]

Challenge 27 Tasks:

• Go through the rules and resources provided by Hacktoberfest
• Explore different open soure repositories where you might be interested in contributing and look at any potential issues you might want to work on for Hacktoberfest
• Share your tips in the issue created in the previous challenges

Submission:

🌐 Repos Participating in Hacktoberfest 🌐

Contribution Guidelines:

Participant Categories:

• Contributors
• Maintainers

Pull/Merge Request Details:

• OUT-OF-BOUNDS: PR/MR should be within time bounds (Oct 01 - Oct 31).
• EXCLUDED: Repos found violating Hacktoberfest Values will be excluded, and contribution to those will not count.
• SPAM: PRs/MRs made shouldn't be spammy.
• PARTICIPATING: PRs/MRs made to only participating repos will be considered. Such repo must have topic HACKTOBERFEST or PR/MR should be labeled HACKTOBERFEST-ACCEPTED.
• INVALID : PR/MRS must not be labeled INVALID.
• ACCEPTED : PR/MRS must be merged, have HACKTOBERFEST-ACCEPTED label, or have an overall approving review.

Once the PR/MRS passes all the above checks, it will be accepted after a 7-Day review period.

MEASURES TO REDUCE SPAM

• Spammy PRs/MRs will be labelled as spam.
• PRs/MRs need to be approved by a maintainer.
• Bad repos will be excluded.
• Low Quality PRs/MRs should be avoided.

[0xStryK3R]

Challenge 24 Update:

• I have requested to be added as contributor for the project deep-translator.
• They are looking to build website/api for the deep-translator package. I have requested to contribute for the same.

Challenge 25 Update:

• No update received on the previous request submitted yesterday. Awaiting response from owner.
• Also looking for any other Open source repos I can contribute in as per my skillset - in case above one doesn't pan out. Haven't found anything else yet.

Challenge 28 Update:

• No update received on the previous request submitted. Awaiting response from owner.
• Had also submitted a new request on a different repo just in case. Owner has assigned me to pick it up, and I have started working on the same.
  

[0xStryK3R]

Challenge 29 Submission:

• Idea Pitched: Data Structures And Algorithms Repo
• Screenshot:
  

[0xStryK3R]

Challenge 30 Submission:

This was one of the best challenges I have participated in! Learnt a lot about Open Source Contribution, and looking forward to start my own open source journey. Also looking forward for more of the promised events! 😀

[0xStryK3R]

Milestone 4 Post Link!

[kuraakhilesh8230]

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