maverick/docbrown
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
docbrown/docs/getting-started/forking.md
Andy Zhao 955bdcb2bc
Update docs with Forem instead of dev.to (#9316) 
* Rename all GitHub links from thepracticaldev/dev.to to forem/forem

* Use new site name

* Rename to Forem

* Rename more dev.to to forem

* Remove unnecessary redirects

* Rename DEV to Forem

* Use Forem instead of DEV for branding

* Use Forem instead of DEV for licensing

* Use seedling instead of DEV logo
2020-07-15 13:29:11 -04:00

1 KiB
Raw Blame History

title
Forking the Repo

Forking the repository

The first step in contributing to any Open Source project on GitHub is forking so that you can create Pull Requests. If you're not familiar with the idea of forking a repository, GitHub has a super simple tutorial!

If you're ready to get started, fork Forem's repository!

Once you've got a fork on GitHub, you can clone your fork to run the project locally:

git clone https://github.com/<your-username>/forem.git

As time goes on, you may need to refresh your fork. If you have trouble with that, you can read about keeping a fork caught up on Forem!