scaler-september-open-source-challenge-2022
scaler-september-open-source-challenge-2022 copied to clipboard
scaleracademy
Challenge 1-30
URL of your forked repository : https://github.com/Rishav986/scaler-september-open-source-challenge
A screenshot of the cloned project in your system :
Screenshots for challenge-17.
Created a Readme file.
Published Repository.
Created new branch.
Created new Pr.
Link for project board (challenge- 20) - https://github.com/users/Rishav986/projects/1/views/1
Link to the repo - https://github.com/Rishav986/Java-assignments
Link for project board (challenge- 20) - https://github.com/users/Rishav986/projects/1/views/1
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 and there is no repo link of this challenge complete this by sunday
Link for project board (challenge- 20) - https://github.com/users/Rishav986/projects/1/views/1
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 and there is no repo link of this challenge complete this by sunday
Hey @kuraakhilesh8230 Done as you mentioned.
Challenge 23
My key points to keep in mind while contributing to open source:
Issues:
- Always create a new issue, if you have some new idea, stating what we want to change with a proper description.
- Use labels to check status of the issue.
- Good-first-issue labels are a suitable for beginner's in open source contribution.
- Notify others that you are working on the issue by comments, it will decrease conflicts b/w contributors.
Branches:
- Main/Master-Default and stable branch are important branches.
- The branch name can include a bug, fix, WIP, the issue it will solve, author name, etc.
- Don't use too long descriptive names.
- Use unique id's in branch name.
Pull Request:
- Write appropriate commit messages and PR descriptions.
- Give your Pr a descriptive title.
- Always review your PR before assigning it .
- Keep Pr short.
congrats you have completed the milestone-2 successfully and you are good to go🎉
Challenge 25
Finished the task assigned for contribution, and created pull request get merged too.
Currently searching for more compatible issues for contribution purpose.
Challenge -26
Will register when the link will be available, also looking for new projects to contribute.
Challenge 27
I have registered for Hacktoberfest 2022 as a contributor
Tips for Hacktoberfest :
- Contribute to repo containing the “hacktoberfest” label.
- If you are new to hacktoberfest contribution, look for issues with the good first issue tag.
- Don't just create PRs for solely benefits.
- At least 4 PR should be accepted between 1 Oct to 31 Oct for rewards in hacktoberfest.
- Create new issues if you know something you can try to add new features or improvements in existing repo.
Challenge 28
Searching for good issues/repos of my interest, till then trying to contribute some basic program stuff.
Will start contributing to some android development related projects, currently looking for them, which matches with
my knowledge of android.
Challenge 30
Today is the final day of this open source challenge. I enjoyed this month long journey of learning git, from zero to having somewhat good knowledge about github. I want to thanks scaler for providing such great guiding challenges. And I would love to participate in more such challenges.
Now, I feel ready to start off my journey with Hacktoberfest, and will continue to contribute in more such challenges.
Challenge 29
Started a new discussion with an idea.
Upvote any ideas which is there in discussion and attach that screen shot also atleast 1 is enough
Challenge 29
Started a new discussion with an idea.
Upvote any ideas which is there in discussion and attach that screen shot also atleast 1 is enough
Hey @kuraakhilesh8230 added screenshot for some upvoted discussions.