Skip to content

Releases: cpina/github-action-push-to-another-repository

v.1.7.2

19 May 21:35
Compare
Choose a tag to compare

Fix #102

It caused the following error message when using the personal access token (which uses https:// to connect to GitHub):

[+] Pushing git commit
error: RPC failed; HTTP 408 curl 18 HTTP/2 stream 7 was reset
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly

v.1.7.1

19 May 14:55
Compare
Choose a tag to compare
v.1.7.1 Pre-release
Pre-release

Fix error if create-target-branch-if-needed was used and the target repository already had the target branch

v1.7

07 May 15:42
Compare
Choose a tag to compare
v1.7 Pre-release
Pre-release

New feature to create the target branch if it does not exist

Use variable: create-target-branch-if-needed

Thanks damiencornu.

v1.6

25 Feb 22:01
0a14457
Compare
Choose a tag to compare

Add support for git-lfs (thanks Travis for helping testing it).

Fix push using SSH keys for GitHub enterprise

05 Sep 22:41
Compare
Choose a tag to compare

Fix error on push when using SSH keys using GitHub enterprise (a server that is not github.com)

It also links to the new documentation: https://cpina.github.io/push-to-another-repository-docs/

Add support for deploy keys (SSH keys)

27 Jun 10:07
Compare
Choose a tag to compare

Support added for SSH deploy keys.

Previously the action was pushing into the destination repository using the personal authentication token. In addition to supporting the use of the personal authentication token (no configuration changes required), there is now the option to use SSH deploy keys. This allows access to be given only to a specific destination repository.

Fix fatal: unsafe repository ('XXXXXX' is owned by someone else)

13 Apr 08:19
ac0bb2c
Compare
Choose a tag to compare

Fix "fatal: unsafe repository ('XXXXXX' is owned by someone else)"

Thank you all participants in #64 for your help.

v1.4.1

21 Jan 16:46
Compare
Choose a tag to compare

Fix target-directory functionality

When using target-directory the version v1.4 created a directory named "1". This release fixes it.

Apologies for the bug.

(contains bug) Allows to specify the target directory

20 Jan 22:47
164a872
Compare
Choose a tag to compare

Main change: new option (target-directory) to specify the target directory in the destination repository

Update: the feature target-directory created a directory named "1" instead of your name. Please use version v1.4.1 or newer.

Copies files starting with ., add checks, improve documentation

25 Apr 10:36
Compare
Choose a tag to compare
  • Files starting with "." in the source-directory are copied to the destination-repository-name. This has been the case in the master branch since December but it wasn't included in the previous release.
  • Renamed the branches of this project's GitHub repositories to main, updated the documentation, etc. Note that the target-branch default value is still master for historical reasons, for now please set it to main if needed in your project.
  • Updated documentation: this should help new users of the GitHub Action.

Thanks to everyone who opened issues, it has helped improving the GitHub Action (documentation or behaviour).

Apologies for the long time between releases: I have been very busy with other things.