scaler-september-open-source-challenge-2022
scaler-september-open-source-challenge-2022 copied to clipboard
scaleracademy
Dhruv6606
Fork URl: https://github.com/Dhruvbagadiya/scaler-september-open-source-challenge.git
challenge-20
Do challenge 20 correctly and attach screen shots of all the files of your project which should show done after moving from inprogress
Congratulations you have successfully completed milestone-2 and you are good to go🎉
In Open source project we make contributing file and contribute from any repository,Even If you don't know about the coding than its fine it doesn't matter to contribute but ya if you know coding it will help you a lot in this contributing open source.
contributions are like a giving our work's description and its mostly in README files and in description you give a guidance of your project and a direction of the path which helps anyone to solve things, Adding images or Outputs to show how to work project or a code.
1] ISSUES If you get or find any issue while running the code,Check if there's an issues already exists for the same or not? and if there isn't any then you should create one, and if there exists then if you wish to work on that you can ask to assign it to you. once you're assigned an issue work on that. They may have provided guidelines for contributing to a project, if there isn't any we should follow some standard guidelines.
2] BRANCH NAMING There are two types of branches,First is main which is Regular and Second are Temporary Branches ex: features and bugs etc.
3] COMMITS Give Commits active and descriptive title, because it will help further if there found a situation where you have to go backward and reset to previous code-base then if you have given right and meaningful commit message you can easily find it.
4] GIT BRANCH It is very important and powerful but you have to use it or manage it correctly and effectively. You can make branch to do separate work in same repository and the work is maybe temporary and if it is important you have to merge that branch to main.
4] PULL REQUEST Pull request is a part of collaborative workflow, and through pairing We should follow and provide some meaningful description and features lists that we have implemented or bug fixes that we had done. We should also share some examples and some functionality demonstration video or instructions, it will save lots of time of maintainers, testers, QA s,contributors.
CHALLENGE-24
I Have been assigned 2 Issues
I have done my first algorithm task Ford-Fulkerson and I have created pull request and waiting for review Pull request https://github.com/PrakashGatiyala/hackerrank_problems-or-hackerearth_problems/pull/159
I have requested for hexagonal close issue and i assigned today Hexagonal-issue and i am working on it
Challenge : 27
Hecktoberfest-2022
PR/MRs must be created between October 1 and October 31 and PRs must be made to public, unarchived repository. PR/MRs that their system detects as spammy will also not be counted. User with two or more spammy PR/MRs will be disqualified. PR/MRs must be tagged “HACKTOBERFEST” or must be labeled “HACKTOBERFEST-ACCEPTED". PR/MRs must not be labeled as "INVALID". PR/MRs Must be merged or have an overall approving review.
Challenge - 28
https://github.com/web-tiki/responsive-grid-of-hexagons/pull/41
Created Pull Request and Edit Some Small Changes In Code And Want to Edit some Gradients in code working on it.
Finally Completed Open Source Challenges , It Was Wonderful Experience To Complete Daily Tasks and this is last day of challenges. I have very basic knowledge about Github but by completing this challenges feel like pro. Thank you for This Project and also thanks to our scaler-discord Community.
