Git push local changes
In Designer, you save or commit your changes to your local copy of the branch. This allows you to have an isolated workspace where there is little risk of collaborators overwriting each other's work. Use the Push local changes action when you're ready to upload your local commits to the remote repository so that they're available to others who are collaborating on the same project. Pushing your local changes to the remote repository ensures that your pipeline code is backed up in a central location and collaborators are working with the most up-to-date code.
| Property | Description |
|---|---|
| Changes | For information only. Displays the number of commits in your local workspace that you can push to remote. |
| Commit messages | For information only. Displays a list of commit messages, including timestamp and commit author. |
| Publish | Check to enable publishing of pipelines. Publishing makes pipelines available for scheduling. Existing schedules with Always use latest selected in the Artifact dropdown when the schedule was created will run the updated published pipeline. Read Artifacts to learn more. |
| Environment | If Publish is checked, select the environment in which the artifact will be published and deployed. A schedule can then be created to run a specific published pipeline in the selected artifact from an environment, at set intervals. Read Add environment to learn more about environments. |
| Version name | If Publish is checked, enter a name for the version being pushed to remote. This version name will be used to identify the artifact that will be built and deployed to the specified environment. The name must be unique in the environment being published to. The name can include alphanumeric characters and the following special characters: - _ . ! ~ * ' ( ). |
| Recent version history for environment | Displays the most recent artifact versions published in the selected environment. Includes the publish timestamp. |
| Include shared pipelines | Select this to publish a new version of all shared pipelines in the project. When new versions of shared pipelines are published, they become available to all projects and environments, and any pipelines using [Latest] will run the updated version. |
Note
The version name that you choose when publishing must be unique, because it will be used to identify the artifact that will be built and deployed to the specified environment.
We recommend using a semantic versioning naming scheme that uses a combination of major and minor version numbers to track subsequent versions. For example, 0.1, 0.2, 1.0, 1.1, 2.0, and so on.
How to push and publish local changes
Once you have made commits in your local branch, you can push your changes to the remote version of your branch.
- Click the branch menu on the project bar.
- Click Push local changes in the drop-down menu. The number displayed next to this option shows the number of committed changes that haven't been pushed yet. The Push local changes panel will open, displaying the list of local commits that you can push to remote.
- If you want to publish your pipelines to make them available for scheduling, check the Publish checkbox and complete the required fields as described in the table above.
- Click Push to save all your local commits to the remote repository. Otherwise, click Cancel to cancel your push.
After pushing your changes and publishing your pipelines, you can then create a schedule to run either the latest version of a pipeline, or a specific version of a pipeline. In the Data Productivity Cloud, each version of a pipeline is part of a unique artifact, which is used in schedules. For more information about how to create and manage artifacts, read Artifacts.