Open sankalp-srivastava opened 2 years ago
url : https://github.com/sankalp-srivastava/scaler-september-open-source-challenge screenshot :
Challange 3
Challenge 4
Challenge 11 : new branch
Challenge 13
Good to go verified ✅
Challenge 14
Challenge 16 : merge Fix
Challenge 17
challenge 20
Challenge 21
challenge 20
do challenge-20 correctly because all the screen shots should be attached starting from todo to done and in atlast the screen shot should show done with tick marks for all the files complete this by sunday
Challenge 20
@kuraakhilesh8230
Branches Git Branching Naming Convention
Start branch name with a Group word
Use Unique ID in branch names
Use Hyphen or Slash as Separators
Git Branch with Author Name
Avoid using numbers only
Avoid using all naming convention simultaneously
Avoid long descriptive names for long-lived branches Pull Request
Give your feature branch a clear name
Give your commits and PRs 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 Contribution Guidelines
make extensive use of issue labels to designate the priority, status and beginner-friendliness of various issues. We have a standard set of labels across all projects CONTRIBUTION PROCESS Once you've found an issue you'd like to work on, please follow these steps to make your contribution:
Comment on it and say you're working on that issue. This is to avoid conflicts with others also working on the issue. If you've followed the guidelines above, you don't need to ask permission to start work on an issue.
Write your code and submit your pull request.
Wait for code review and address any issues raised as soon as you can. PROPOSING A NEW ISSUE
Create a new GitHub issue associated with the relevant repository and propose your change there. Be sure to include implementation details and the rationale for the proposed change.
We are very reluctant to accept random pull requests without a related issue created first.
The issue will automatically have the 🚦 status: awaiting triage label applied. Wait for a project maintainer to evaluate your issue and decide whether it's something that we will accept a pull request for.
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.
Challenge 20
@kuraakhilesh8230
congrats you have completed the milestone-2 successfully and you are good to go🎉
Challenge 24: still looking for project to contribute using my python skills. most of the projects are above my skill set level but i am still looking
Challenge 25
Created a pull request in open souce project of design and code : https://github.com/Design-and-Code/Opensource-practice/pull/38 Waiting for approval or changes required.
Some tips for Hacktoberfest 2022.
not done challenge-26 pls do it asap to avoid rejection
Challenge 26.
registered on day 26. there was no info to post a pic for profile so adding it now @kuraakhilesh8230
contributing in open source project. Made my pull request https://github.com/Design-and-Code/Opensource-practice/pull/38 I have been asked to make some changes before merge and I am working on that
Congratulations you have successfully completed milestone 3 and good to go 👏
I have successfully completed the Scaler-open-sourcechallenge organized by Scaler . I will continue my open source journey and will first time contribute in Hacktoberfest, excited and hoping for the best. I got to learn about some new git tools and commands.
Also a special thanks to @kuraakhilesh8230 @DaltonDeven for helping me from time to time and @shivaylamba for these various intresting challenges.
I will surely encourage, my other friends, to contribute to open source and improve their knowledge.
congrats you have completed milestone-4 successfully and you are good to go🎉
name: Sankalp Srivastava github_user_name: sankalp-srivastava