You only need to run this command with the -u parameter the first time.
$ git remote add origin Next, push the code from your local repository to your new remote repository. In the last line below, swap in the path to your repository from Step 6. We’ll rename origin to upstream and add the new empty repo we created as the origin.
Clone your forked repository to your local machine (must be on campus or connected to Yale VPN).You can verify the Jenkins job is working with following steps: It takes about 15 minutes for code to be deployed. Next, request a Jenkins deployment job be created for your site.Īfter your Jenkins job has been set up, code pushes to your fork will automatically trigger a deployment of the updated code to your dev site.After the fork is built, click the Settings link in the right sidebar and rename the fork to match your site name in dev:.To generate your fork, use the Fork button at the top right of the repo. This is the master repository for Drupal 7 at Yale. You must fork the main Drupal 7 repository to begin working with code. The user now has access to all repositories inside the organization.Enter the user’s Yale NetID or first name to add them as a team member.
At the top left, click on your username to change your account context, and pick your organization.The user must first log in to Github:Enterprise using their Yale NetID to create an account. If there are other users who need to access a repo, they will need to be added to your organization.
You will not be billed as this is just used for organization owner contact. Put your email address in the Billing Email field.Give your organization a short name to identify your department or group.From your account settings, click Organizations > Create new organization.
You can use the support links at the top of the SSH key page if you need a tutorial.
You have a command line Git client installed or use Windows / Macgraphical tools.Github:Enterprise is used to interact with code for custom theming and site building.