-
Notifications
You must be signed in to change notification settings - Fork 490
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #10219 from IQSS/10218_update_sphinx_action
OdumInstitute is now UNCCH-RDMC
- Loading branch information
Showing
2 changed files
with
5 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -291,16 +291,16 @@ By default, when a pull request is made from a fork, "Allow edits from maintaine | |
|
||
This is a nice feature of GitHub because it means that the core dev team for the Dataverse Project can make small (or even large) changes to a pull request from a contributor to help the pull request along on its way to QA and being merged. | ||
|
||
GitHub documents how to make changes to a fork at https://help.github.com/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork/ but as of this writing the steps involve making a new clone of the repo. This works but you might find it more convenient to add a "remote" to your existing clone. The example below uses the fork at https://github.com/OdumInstitute/dataverse and the branch ``4709-postgresql_96`` but the technique can be applied to any fork and branch: | ||
GitHub documents how to make changes to a fork at https://help.github.com/articles/committing-changes-to-a-pull-request-branch-created-from-a-fork/ but as of this writing the steps involve making a new clone of the repo. This works but you might find it more convenient to add a "remote" to your existing clone. The example below uses the fork at https://github.com/uncch-rdmc/dataverse and the branch ``4709-postgresql_96`` but the technique can be applied to any fork and branch: | ||
|
||
.. code-block:: bash | ||
git remote add OdumInstitute [email protected]:OdumInstitute/dataverse.git | ||
git fetch OdumInstitute | ||
git remote add uncch-rdmc [email protected]:uncch-rdmc/dataverse.git | ||
git fetch uncch-rdmc | ||
git checkout 4709-postgresql_96 | ||
vim path/to/file.txt | ||
git commit | ||
git push OdumInstitute 4709-postgresql_96 | ||
git push uncch-rdmc 4709-postgresql_96 | ||
.. _develop-into-develop: | ||
|
||
|