scaler-september-open-source-challenge-2022
scaler-september-open-source-challenge-2022 copied to clipboard
scaleracademy
Challenge (30/30)
https://github.com/BishalBiswal/scaler-september-open-source-challenge
challenge 9
BishalBiswal-2.md was removed
challenge 11
challenge 13
challenge 20
repo link : https://github.com/BishalBiswal/banana
board link : https://github.com/users/BishalBiswal/projects/1
Challenge 23: Branches:
- Regular Branch - 3 permanent branches will be there, they are master : main development branch dev : It's for development, so no direct changes are made in master QA: This is for QA testing
- Starting branch name with group word is ideally good for identifying what one is doing, group word can be anything to match your workflow like Bug or WIP. For e.g. Bug – The bug which needs to be fixed soon WIP – The work is in progress, and I am aware it will not finish soon
- Using unique tracker ID in branches is good when fixing bugs.
- Separators like -, /, _ are good as they increase the readability and avoid confusion. They should be consistent.
- Author names are added generally to track different developers' works.
- Avoid using very long and descriptive names, all naming convention simultaneously.
Creating a pull request:
- Giving clear branch names. If multiple contributors are there, adding initials allows you to filter down to your personal branches.
- Giving commits and pull requests clear names and descriptive titles.
- Streamline your process of creating a new PR using functions.
- PRs should have a meaningful description which includes what, why and how.
- When possible functionality should be shown visually, it helps give preview at a glance.
- Reviewing PR before assigning to ensure everything runs properly and caught up.
Issues:
- A good place for beginner's would be issues with a good first issue tag or use issue finder tool.
- Make sure it's not marked staff-only or not ready for work.
- Once a required repo has been found, add a comment asking one of the maintainers to triage the issue and label it as appropriate. 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.
- If proposing a new issue: -Create a new issue in the repo with proposal. -The issue will automatically have the 🚦 status: awaiting triage label applied. Maintainer will review whether to accept pr or not. If accepted, work can be started.
Challenge 25: I'm still searching for a suitable issue to contribute to, I've found a few repositories that I can contribute to.
Challenge 26: I've found 2 repositories where I can help by contributing. I've added comments in issue
https://github.com/vicky002/AlgoWiki/issues/65#issuecomment-1258584305
https://github.com/PaceHut/Pacehut-calci/issues/8#issuecomment-1258304759
and I'm waiting for reply, I've also registered for hacktoberfest.
you didn't gave your pr link in form rather you gave scaler open source challenge repo link ,pls give correct link to get it verified successfully
I have registered in Hacktoberfest already. I have gone through the guidelines and I have shortlisted a few repos I want to commit Only PRs made between Oct 1 - 31 count toward hacktoberfest progress. So no commits have to be done right now. Contributions must be made to public repositories. PRs shouldn't be spammy
Challenge 28: I've commented in 2 repos beforehand and waiting for reply, I have commented in one more repo I want to commit to today.
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.