Welcome to this growing project of contributors and content and synergy with the common goal or expanding the threshold of learning to code. With a focus on psychological development and adult learning, this diverse group of developers, engineers, educators, and other experts come together to provide ANYONE the tools they need to learn to code. We are not alone either! We there are other teams around the world with the same focus and understanding in the importance of education, and we are ready to join forces to help build the future of technology today while keep anyone who wants to be, in the loop.
Join the Discord Server here.
If you find an issue and want to report it, GREAT! THANKS! Please include the following when reporting the issue: - Title and description of the issue - Useful tags, if any. - Anything, if applicable, that explains or reproduces the issue. - HAPPY HACKING!CLICK HERE (which starts at 2:45:00) for a great tutorial from Leon Noel of #100Devs on cloning, creating branches, pushing to your own branch, and making a pull request from your remote branch to the original repo's remote branch. More or less all you need to know to start contributing.
There are more specifics depending on the project's guidelines as all have their own ultimate set of rules. This repository sticks to pretty standard practices when it comes to contributing.
Fork this repo & clone to your local machine:
git clone https://github.com/mathcodes/lc_hr_cw.gitNavigate to project directory.
cd lc_hr_cwCreate a new Branch
git checkout -b my-new-branchAdd your contribution
git add .Commit your changes.
git commit -m "Relevant message"Then push to your remote branch
git push origin my-new-branch
Create a new pull request from your forked repository to the original repository and a maintainer will review it and either accept it, leave notes to fix some things, or close it (hopefully with notes with reasons. If any PRs are closed in this repo, there will be an explanation, an option to makes changes are submit a new one, or I will also make time to walk through the solution with you over a call!
feat-<description>
For example, for this issue, the commit message would be as follows:
feat-bug_correction
or something similar starting with feat-.
That will do the trick at this stage of development. Let me conclude this guide by emphasizing my efforts to make myself accessible, and listen to advice, be ciriticized if I'm messing up, don't hold back, but maintian respectful, professional attitudes at all times. Speak up! Submit a PR!!! I bet I'll accept it!
Thanks for reading and expressing interest in our journey to bettering the education of developers!