@@ -2,13 +2,13 @@ Git fork/PR workflow
22-------------------- 
33This repository uses the [ forking model] ( https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow ) 
44for collaboration. In this model,
5- each developer forks the main (sorgerlab /indra) repository, pushes code
5+ each developer forks the main (gyorilab /indra) repository, pushes code
66only to branches in their own fork, and then submits pull requests to
7- sorgerlab . After cloning your own fork of ` indra ` , you should add ` sorgerlab ` 
7+ gyorilab . After cloning your own fork of ` indra ` , you should add ` gyorilab ` 
88as a remote to be able to track the latest changes by doing
99
1010``` 
11- git remote add sorgerlab  https://github.com/sorgerlab /indra.git 
11+ git remote add gyorilab  https://github.com/gyorilab /indra.git 
1212``` 
1313
1414When a PR is submitted from a branch, any further changes can be pushed
@@ -17,9 +17,9 @@ are automatically appended to the PR. Please always check the box on Github
1717allowing the maintainers of the repo to make changes to the PR.
1818
1919In addition, as a convention, we only merge PRs whose branches are rebased
20- on top of the latest sorgerlab /master. This means that instead of merging
21- sorgerlab /master into your own branch to resolve conflicts, you should always
22- rebase on top of sorgerlab /master and force push your branches if
20+ on top of the latest gyorilab /master. This means that instead of merging
21+ gyorilab /master into your own branch to resolve conflicts, you should always
22+ rebase on top of gyorilab /master and force push your branches if
2323needed (you can do this even if a PR from that branch is already open).
2424Consistent with this convention, in general, you should not use ` git pull ` 
2525to update your local fork. Rather, use ` git fetch --all ` ,
@@ -32,7 +32,7 @@ some commits before merging.
3232
3333Pull requests
3434------------- 
35- Always submit PRs via the sorgerlab  repository.
35+ Always submit PRs via the gyorilab  repository.
3636Give your PR a concise and clear title that describes without excessive detail
3737what the PR does. You should give more details in the description, pointing
3838out the important changes made and any additional remarks that are relevant.
0 commit comments