### What it does This action pushes commits from Git repository connected with Buddy (GitHub, Bitbucket, GitLab, private Git server) or from Buddy’s built-in Git server to another repository with or without artifacts saved to the pipeline’s filesystem. ### How it works The action pushes a revision to a remote branch with which it was executed. By default, it pushes from the pipeline filesystem. It means that it will also push a commit containing artifacts that were generated in the filesystem by previous pipeline steps. ### Git Push Action Features - You can process the files from the repository. - You can create a tag during the execution and push it to the repository. - You can push changes to the same repository that the project is synchronized with without the need of authorizing it in the action. - It’s possible to include pushing tags - If Don't deploy changes made by previous action is set, changes made by other actions in the pipeline filesystem, will be ignored like changed files or generated artifacts - The action uses `.gitignore` from the repository by default, but it’s possible to set custom `.gitignore` in the action settings. The option could be used to push artifacts that we don’t want to store in the repository - It’s possible to select different branch to push - When Without force is selected, this action will fail on conflicts - Commit message for committed artifacts is settable - Both, HTTP and SSH authentication are supported - Input fields: URL, Login, Password, Commit Message support [Environment variables](https://buddy.works/docs/pipelines/environment-variables) - The action can be configured in [YAML mode](https://buddy.works/docs/yaml/yaml-gui). See [${action.name} YAML parameters](https://buddy.works/docs/yaml/yaml-actions/git-push) and [${action.name} YAML config example](https://buddy.works/docs/yaml/yaml-actions/git-push#yaml-example-for-git-push) - Buddy's [${action.name} API](https://buddy.works/docs/api/pipelines/create-manage-actions/add-action/git-push) is supported - The action supports conditional execution: it can be run on each execution, only if there are changes in the repository or specific paths since last execution, or if an environment variable has a specific value - Error handling: you can either stop the execution, mark action and pipeline as failed or proceed the execution, mark action as warning and jump to the next action ### More about ${action.name} * [Getting started with CI/CD for ${action.name}](https://buddy.works/docs/deployments/git-push)

Git Push

Git Push Tutorials

Semantic Versioning