... | ... | @@ -20,7 +20,7 @@ We've used the `MBDA Drupal 9` project as an example below - but these steps can |
|
|
1. Choose your namespace/account to create a fork.
|
|
|

|
|
|
1. This newly created fork will be something like `https://git.commerce.gov/<your namespace>/mbda8` . Hereafter this is referred as `MBDA Drupal 9 Fork` in these instructions. This will be your downstream project where we will be working on and committing changes to the upstream project - https://git.commerce.gov/enterprise_applications/mbda8
|
|
|
1. Setup your SSH Key for pulling and pushing code from your local environment to our our code repositories in GitLab (see [Gitlab and SSH Keys](https://git.commerce.gov/help/ssh/index.md)) **PLEASE REACH OUT TO OUR SYSADMIN IF YOU NEED ASSISTANCE WITH THIS STEP**
|
|
|
1. Setup your SSH Key for pulling and pushing code from your local environment to our our code repositories in GitLab (see [Gitlab and SSH Keys](https://git.commerce.gov/publicgroup/documentation/-/blob/master/documents/authentication_with_ssh_keys.md)) **PLEASE REACH OUT TO OUR SYSADMIN IF YOU NEED ASSISTANCE WITH THIS STEP**
|
|
|
1. Create and navigate to a local `Sites` directory and clone your `MBDA Drupal 9 Fork` by running the command:
|
|
|
`git clone git@git.commerce.gov:<yourforkname>/mbda8.git mbda_d9`
|
|
|
* This will clone your `MBDA Drupal 9 Fork` codebase inside your local `Sites` directory entitled `mbda_d9` and defaults to [Master] branch. E.g `Sites/mbda_d9`
|
... | ... | |