Skip to main content
In , 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.
The version name that you choose when publishing must be unique to your project, because it will be used to identify the artifact that will be built and deployed to the specified environment. If you select the Include shared pipelines checkbox, any shared pipelines will be given a project prefix to identify them.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.
  1. Click the name of your branch on the project bar.
  2. 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.
  3. 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.
  4. Click Push to save all your local commits to the remote repository. Otherwise, click Cancel to cancel your push.
After you have pushed your changes to the remote branch, a notification appears with a link to create a pull request in your Git repository. If your team has a pull request approval workflow, you can click this link to be taken to your external Git repository and create a pull request containing these changes. 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 , 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.
  • It’s good Git practice to pull before you push. This will update your local branch with any new changes that may have been pushed to the remote from other contributors.
  • Remember to push your local changes first before merging changes to another branch.