scaler-september-open-source-challenge-2022
scaler-september-open-source-challenge-2022 copied to clipboard
scaleracademy
Challenge 1-30: VividhPandey003
URL of forked repository: https://github.com/VividhPandey003/scaler-september-open-source-challenge
Cloned Project Screenshot:
Challenge 17: Committing, Branching, Pull, Push using github desktop
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
Tasks moved In progress column
Done with the In progress task and moved the card to the Done column
Congrats you have successfully completed milestone 2 and you are good to move onto next milestone All the best✅️
Challenge 23
Issue creation
- Use Issue Finder tool to find a good issue that matches your skills.
- Check the issue comments/labels to see whether someone else has indicated that they are working on it.
- Once you've found an issue you'd like to work on then comment on it and say you're working on that issue.
- Write your code and submit your pull request.
- Wait for code review and address any issues raised as soon as you can.
Git Branching Naming Convention
1.Start branch name with a Group word. 2. group word can be anything to match your workflow like Bug or WIP. 3. Use Unique ID in branch names. 4. Use Hyphen or Slash as Separators because it maked the git branch name readable. 5. We can also add Author Name to our branch name. 7. Avoid using numbers only and also avoid using all naming convention simultaneously. 8. Avoid long descriptive names for long-lived branches.
Creating a pull request
- Give your feature branch a clear name.
- Give your commits and PRs an active and descriptive titles.
- Streamline your process of creating a new PR.
- Give your PR a meaningful description.
- Show your functionality visually, whenever possible.
- Review your own PR before you assign it to others.
Challenge 24
Commented on the issue for contribution.
Eagerly waiting for their reply as the project is really cool⭐️⭐️⭐️⭐️⭐️
Challenge 25
Still working on the issue
Trying to figure out how to fix the issue.
Challenge 26: Will register for Hacktoberfest as soon as the Registration Form opens.
Commented on more repositories. Waiting for the maintainers to assign me the issue. Got assigned another issue. Will be resolving it under Hacktoberfest
(Turns out the old repository where I commented was dead since a long long time)
Challenge 27: Registered for Hacktoberfest as a Contributor.
Checked out many repositories. Using 'Labels' made searching for issues much easier.
- Contribute to Repositories labelled with 'hacktoberfest'.
- Make atleast 4 valid pull requests to complete Hacktoberfest.
- Avoid submitting low quality pull requests/spammy PRs.
- QUANTITY IS FUN, QUALITY IS KEY
- Open Source is not just about learning Github and contributing for the sake of it, it is more like learning, connecting with developers and helping each other.
congrats you have completed milestone-3 successfully and you are good to go🎉
Challenge 28
Got assigned with two issues. Waiting to submit a pull request as soon as Hacktoberfest starts. Commented on another issue, waiting for it to be assigned.
Challenge 29:
Really liked these project ideas. Thus upvoted them.🚀🚀
Challenge 30 : Completed all the challenges of 30 days open source challenge. It was very amazing and a great learning experience. Thank you for giving me such a wonderful opportunity.