Open nightfury-crypto opened 2 years ago
CHALLENEGE 2
fork link - https://github.com/nightfury-crypto/scaler-september-open-source-challenge
screenshot of clone
screenshot of all branches
challenge 4
sync fork done in local machine
Challenge 5
challenge Done -->
Challenge 9
Created new branch under previous branch
Challenge 13 - git stash
deleted from stash
Creating a conflict
resolving the conflict -- edit the merge.txt file in the file editor and removed the ======= signs and committed it
pull request
Challenge 17 created a new repository and added the following files
https://github.com/nightfury-crypto/github-desktop-quicklook/
one todo item is done
Board is created -->
repository link - repo project todo borad link - project board
all alias I created
git config --global alias.logp "log --pretty=oneline"
git config --global alias.newbr "checkout -b"
git config --global alias.csf "commit -s -m"
Summarizing open source contribution best practice. ( in my words)
Before contributing into any repository first check out the guideliness of How to contribute inside the repository. You can find it in the README.md
file or there will be a separate CONTRIBUTING.md
file. Go through it and follow it.
Open a new issue
Before opening a issue make sure no one already working on that issue by searching it. If you have not found any opened issue of same task as you then good to go --> Open a new issue with a precise/appropriate title and description so that it can be understood.
NEW ISSUE
good first issue
or help wanted
- these labels are for participating in contribution but, if
staff-only
label is there then you are not allowed to contribute as these are for the staff only.Once the issue gets approved and the task is assigned to you start to work on the task. Fork the repository and set up the repository in you system locally.
create a new branch.
BRANCH
Branch is a very important part of github contribution - (permanent branch and temporary branch)
by default there is one master
branch.
1) Permanent Branch -
master
branch - default branch or main branchdev
branch - indicates development branchQA
branch - for testing purpose (before changes go for production)2) Temporary Branch - (which might be deleted after a particular task like bug fix)
bugfix
branch - it indicates that this branch is for bug fixing.wip
branch - work in progress.(note not to include &
or $
sign while naming branch name. go through this link
branch name can be written as like what the purpose of branch along with the issue id.
example - wip-399-responsive-web
after completing the code it's time for pushing the changes and creating a new PULL REQUEST
PULL REQUEST
Try to write a descriptive title and try to describe what your pull request is all about and also mention the issue it belongs to like
#399
so that if your PR got merged into the maintainer can close it.
1) Always try to add a README.md file having full details of what the above code is all about and how to run it or use it or contribute in it. 2) Practice git commands so that you can learn them as they are very important. 3) Sync changes from the remote repository before working. 4) Commit by signoff 5) Create a .gitignore file so that unneccessary files do not get pushed in the Github repository.
These are just few or maybe very little points but these are the most important one I think so. Happy openSource journey.
Task is assigned to me.
- contributing into Twitter OG meta for better SEO.
issue is here - https://github.com/devarshishimpi/Stone-CSS-Website/issues/31 pull request link - https://github.com/devarshishimpi/Stone-CSS-Website/pull/44
pull request got merged
25 september
pnp/cli-microsoft365
- good first issue
Update -
got assigned. Working on it.
Opened a pull request waiting to get it merged successfully. --> https://github.com/pnp/cli-microsoft365/pull/3704
You can see this on - https://stonecss.com/
PR got merged.
here -->
https://github.com/devarshishimpi/Stone-CSS-Website/pull/50
Registered in hacktoberfest 2022
Tips from me for hacktoberfest 2022 -
First of all register in between 26 september - 31 october any time or any day. register here.
--> Search for those repositories and issues which are under hacktoberfest.
--> Contribute as per the repository contribution guideliness do not spam
or make invalid PR's.
--> Pull request between october 1 - october 31 will be counted.
--> Total 4 successfull PR is the main target.
--> Your PR merged should have hacktoberfest-accepted
label.
Happy hacking
I've been assigned 3 issues in last 3 days and i have made the PR's as per the issue.
2 of my PR's are merged successfully with a great functionality in the site and one of my PR will be evaluate and approved and will be merged after 1st October (hacktoberfest ) - pnp/cli-microsoft365
Looking for other issues for now and ready to contribute in hacktoberfest and after hacktoberfest too.
Posted a new idea inside a discussion
ION view: AI based interview - link
Going through other ideas
Done with all challenges and it was a great experience. Learnt a lot with these challenges. I had no knowledge of Github command. Now after this challenge i'm very confident on github. Thanks scaler for this amazing challenge. I will continue this open source journey.
name: Karnail Singh Choudhary github_user_name: nightfury-crypto