If you have an existing repository, add GitHub as a new remote by modifying your project repository’s local clone with the following code (where [username] is your GitHub username and [project] is the name of your project):
Click the name of the application you want to connect to GitHub.
In the left menu, click Pipelines. If your application doesn’t display a Pipelines link, contact Acquia Support.
In the Select Source section, click the Choose source link.
Click Configure.
In the Configure Pipelines with your GitHub repository section, click Configure.
Click Connect to GitHub.
In the GitHub user interface, click Authorize to grant access of your GitHub repository to Cloud Platform. Cloud Platform displays a page containing your environment’s Pipelines information.
Click Select GitHub repository.
Select the repository to which you want to connect, and click Continue.
Each time you use GitHub to create or reopen a pull request, push a commit, or push a tag, Cloud Platform executes the pipelinesstart command using the build definition file in the GitHub repository, and then commits the resulting build artifact, named pipelines-build-[BRANCHNAME], to your Cloud Platform repository.
Changing your webhook
To change the webhook in use by your repository:
Note
You can use the following process to also remove the webhook from your repo. In that case, skip the final step in the following procedure.
Delete the webhook associated with your application.
Complete the steps in the earlier connection procedure to reinitialize your repository with the new Acquia application ID and GitHub repository name.
Next step
To operate, Pipelines expects a file in YAML format named acquia-pipelines.yaml to exist in the root directory of your code repository. This build definition file has all the information required for Pipelines to perform the build, including any variables required and the instructions used to perform the build.
If you have an existing repository, add GitHub as a new remote by modifying your project repository’s local clone with the following code (where [username] is your GitHub username and [project] is the name of your project):
Click the name of the application you want to connect to GitHub.
In the left menu, click Pipelines. If your application doesn’t display a Pipelines link, contact Acquia Support.
In the Select Source section, click the Choose source link.
Click Configure.
In the Configure Pipelines with your GitHub repository section, click Configure.
Click Connect to GitHub.
In the GitHub user interface, click Authorize to grant access of your GitHub repository to Cloud Platform. Cloud Platform displays a page containing your environment’s Pipelines information.
Click Select GitHub repository.
Select the repository to which you want to connect, and click Continue.
Each time you use GitHub to create or reopen a pull request, push a commit, or push a tag, Cloud Platform executes the pipelinesstart command using the build definition file in the GitHub repository, and then commits the resulting build artifact, named pipelines-build-[BRANCHNAME], to your Cloud Platform repository.
Changing your webhook
To change the webhook in use by your repository:
Note
You can use the following process to also remove the webhook from your repo. In that case, skip the final step in the following procedure.
Delete the webhook associated with your application.
Complete the steps in the earlier connection procedure to reinitialize your repository with the new Acquia application ID and GitHub repository name.
Next step
To operate, Pipelines expects a file in YAML format named acquia-pipelines.yaml to exist in the root directory of your code repository. This build definition file has all the information required for Pipelines to perform the build, including any variables required and the instructions used to perform the build.
Cloud Platform