Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding basic definitions and meanings #61919

Open
Uma-95 opened this issue Dec 20, 2022 · 14 comments
Open

Adding basic definitions and meanings #61919

Uma-95 opened this issue Dec 20, 2022 · 14 comments

Comments

@Uma-95
Copy link

Uma-95 commented Dec 20, 2022

The README file has information about how to get started and make initial contributions for beginners.

馃悶 Problem
Someone who is an absolute beginner, he/she might wonder what exactly is Fork, Clone, etc., and ends up searching for these words on the internet.

馃幆 Goal
Instead of searching and moving to some other webpage, what if the meanings of these words are mentioned in the README itself, it would be beneficial for the contributor.

馃挕 Possible solutions
The meanings of words like Fork, Clone, Pull request, Branch, and commit can be added to the README file.

@Uma-95
Copy link
Author

Uma-95 commented Dec 20, 2022

@Roshanjossey could you please review this issue and assign it to me so that I can contribute to the same.

@asissharma
Copy link

Should I contribute to this....

@munnokd
Copy link
Contributor

munnokd commented Jan 3, 2023

@Uma-95 I had make pull request of this issue.

@DevRishiJain
Copy link
Contributor

I can make changes. If you guys like

@theranamuskan
Copy link

Please assign it to me so that I can add to it.

@Kandi-Venkatesh99
Copy link
Contributor

@Uma-95 Could you please assign it to me so that I can contribute from my side.

@CBID2
Copy link
Contributor

CBID2 commented Aug 9, 2023

@Uma-95, I'll gladly work this

@Esh07
Copy link
Contributor

Esh07 commented Aug 18, 2023

Hey @Uma-95, thank you for opening this issue and starting a discussion.

There is a reason why not everything is included in the README.md file. Please refer to the 3rd bullet point in #35892 for more information.

Cheers,
Esh

@sidharth-23
Copy link

Can someone tell me how to work on this issue, I'll be glad to contribute.

@AnushkaSharma04
Copy link

I want to contribute to this . Can you guide since its my first contribution.

@DevRishiJain
Copy link
Contributor

@AnushkaSharma04 Happy to help. So, do you want exact one to one steps or just an overview

@AnushkaSharma04
Copy link

@DevRishiJain It would be really helpful if y provide one to one steps ..since I haven鈥檛 contributed to open source yet

@DevRishiJain
Copy link
Contributor

@AnushkaSharma04 Since you asked for a step by step process, Here it is

  1. Fork the First Contributions repository (https://github.com/firstcontributions/first-contributions) by clicking on the "Fork" button on the top right. This will create a copy of the repository in your own GitHub account.
  2. Clone your forked repository to your local machine using git. You can do this by copying the link of your forked repository in the "Code" button and using the command "git clone ".
  3. Add the main repository as a remote called upstream by using the command "git remote add upstream https://github.com/firstcontributions/first-contributions.git"
  4. Set your main branch as master by using "git checkout master"
  5. Pull from the upstream repository to sync your fork with the latest changes using "git pull upstream master"
  6. Create a new branch with a name like "feature/" using "git checkout -b feature/"
  7. Make your contributions by editing some file or adding a new file. Save your work.
    8.Stage all your changes with "git add ." and then commit with "git commit -m ""
  8. Push your changes to your forked repository using "git push origin feature/"
  9. Go to your forked GitHub repository and make a pull request by clicking on "Compare & pull request"
  10. Add some comments explaining your work if needed and create the pull request.

That's it! Your pull request will now be reviewed and hopefully merged. Let me know if you need any clarification on any of the steps.
I think it is enough but if you still need any further assistance you can drop off your @socials will contact you.

@Akash05-kr
Copy link

Can I contribute to this as my first pull request...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.