maverick/docbrown
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update docs to shine more light on bin/setup and bin/startup (#8290)

Browse source
This commit is contained in:
Dmitry Maksyoma 2020-06-06 04:21:53 +12:00 • committed by GitHub
parent 01380c16a8
commit cc0254310c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/getting-started/syncing.md
View file

@ -81,6 +81,9 @@ Push the changes back to your origin feature branch:
git push origin <feature-branch-name>
```
After you've fetched new commits from upstream, run `./bin/setup`, and it will
install new gems, npm packages, update database, and restart Rails server.
## Additional resources
- [Syncing a fork](https://help.github.com/articles/syncing-a-fork/)

10
docs/getting-started/workflow.md
View file

@ -31,6 +31,11 @@ Use this:
- to sync with latest changes from upsteam master before continuing with a new
feature on your current branch
After you've fetched new commits from upstream, run `./bin/setup`, and it will
install new gems, npm packages, update database, and restart Rails server.
Start the app by running `./bin/startup`, if it's not already running.
## Start over / discard all your changes
Sometimes it is neccesarry to start over from the beginning or reset the current
@ -43,3 +48,8 @@ Use this:
- before working on a new feature
- before creating a new branch to make sure to have all the latest changes in
your fork also.
After you've done that, run `./bin/setup`, and it will update gems, npm
packages, update database, and restart Rails server.
Start the app by running `./bin/startup`, if it's not already running.