luke
/
prjxray
mirror of https://github.com/openXC7/prjxray.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Some final edits (fix section level of "Database Updates"). 

Signed-off-by: Tim Callahan <tcal@google.com>
This commit is contained in:
Tim Callahan 2020-11-20 11:37:01 -08:00
parent 7f77e9f2af
commit c502aa029b
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/db_dev_process/newpart.rst
View File

@ -280,12 +280,12 @@ Push to GitHub:
git push origin <new_branch_name>
Then make a pull request. Navigate to the GitHub page for your
``prjxray`` fork/branch, and click the “New pull request” button. Just
making the request will kick off continuous integration tests. Watch the
results and fix any issues.
``prjxray`` fork/branch, and click the “New pull request” button.
Making the pull request will kick off continuous integration tests.
Watch the results and fix any issues.
Database Updates
----------------
~~~~~~~~~~~~~~~~
The process above (steps 4 and 5) will create some new files and modify
some existing files under database/, which is a different repo,
@ -303,7 +303,7 @@ follow one of the approaches suggested in the checked solution of this
StackOverflow
`post <https://stackoverflow.com/questions/25545613/how-can-i-push-to-my-fork-from-a-clone-of-the-original-repo>`__.
You are NEVER going to send a PR on prjxray-db. It is always rebuilt
You are NEVER going to send a pull request on `prjxray-db`. The database is always rebuilt
from scratch. After your changes on prjxray are merged, they will
reflected in the next prjxray-db rebuild. The changes submitted to your
prjxray-db fork are only for your own testing.