When to use this GitHub Action? It can be used if you have a GitHub repository with a directory that you want to push to another GitHub repository using GitHub Actions (automated on push, for example). It is also useful if when using GitHub Actions, you generate certain files that you want to push to another GitHub repository. For example, if you have MarkDown files and want to generate HTML files, then push them into another repository.
Flow:
There are two example repositories:
- Repository 1: using SSH deploy keys (recommended)
- Repository 2: using a personal access token setup
On a push of the repositories (thanks to the file .github/workflows/ci.yml it uses Pandoc to read the MarkDown file main.md (via this step and the example build.sh. build.sh generates the output/ directory configurable via source-directories appears in the output repository.
Please bear in mind: files in the target repository's specified directory are deleted. This is to make sure that it contains only the files generated on the last run.
There are different variables to set up the behaviour:
From the repository that this Git Action is executed the directories that contains the files to be pushed into the repository.
If you have multiple directories in the source repository, you can specify the prefixes in order that each folder will be copied into in the destination folder.
For the repository https://github.com/cpina/push-to-another-repository-output is cpina.
For the repository https://github.com/cpina/push-to-another-repository-output is push-to-another-repository-output.
Warning: this GitHub Action currently deletes all the files and directories in the destination repository. The idea is to copy from an output directory into the destination-repository-name having a copy without any previous files there.
The email that will be used for the commit in the destination-repository-name.
The name that will be used for the commit in the destination-repository-name. If not specified, the destination-github-username will be used instead.
The Username/Organization for the destination repository, if different from destination-github-username. For the repository https://github.com/cpina/push-to-another-repository-output is cpina.
The branch name for the destination repository. It defaults to main.
The commit message to be used in the output repository. Optional and defaults to "Update from $REPOSITORY_URL@commit".
The string ORIGIN_COMMIT is replaced by $REPOSITORY_URL@commit.
If "true", will force push to the target repo. Use with caution.
The directory to wipe and replace in the target repository. Defaults to wiping the entire repository.
The action, entirely executed in your GitHub continuous integration environment, needs to be able to push to the destination repository.
There are two options to do this:
- Create an SSH deploy key. This key is restricted to the destination repository only
- Create a GitHub Personal Authentication Token: the token has access to all your repositories
Someone with write access to your repository or this action, could technically add code to leak the key. Thus, it is recommended to use the SSH deploy key method to minimise repercusions if this was the case.
ssh-keygen -t ed25519 -C "your_email@example.com"(the type ed25519 is recommended by GitHub documentation)- ssh will ask for a file path:
Enter file in which to save the key: write a new file name. I suggest the default directory and as a filename:id_github_name_of_your_repositoryto avoid overwriting a previous file. If you will be using this action for multiple repositories, you might want to generate different keys for each one. - Leave the passphrase empty (otherwise we would need to pass the passphrase to the GitHub Action)
- Go to the GitHub page of the destination repository
- Click on "Settings" (settings for the repository, not the account settings)
- On the left-hand side pane click on "Deploy keys"
- Click on "Add deploy key"
- Title: "GitHub Action push to another repository"
- Key: paste the contents of the file with the public key. This was generated in the "Generate the key files" step and the name is "id_github_name_of_your_repository.pub"
- Enable "Allow write access"barbar
- Go to the GitHub page of the origin repository
- On the left-hand side pane click on "Secrets" and then on "Actions"
- Click on "New repository secret"
- Name: "SSH_DEPLOY_KEY"
- Value: paste the contents of the file with the private key. This was generated in the "Generate the key files" step and the name is "id_github_name_of_your_repository"
You don't need to do this if you chose to set up the deploy keys using the steps above. This method is here for compatibility with the initial approach of this GitHub Action. The personal access token would have access to all your repositories, so if it were to be leaked the damage would be greater.
Generate your personal token following the steps:
- Go to the GitHub Settings (on the right-hand side on the profile picture)
- On the left-hand side pane click on "Developer Settings"
- Click on "Personal Access Tokens" (also available at https://github.com/settings/tokens)
- Generate a new token, choose "Repo". Copy the token.
Then make the token available to the Github Action following the steps:
- Go to the GitHub page for the repository that you push from. Click on "Settings"
- On the left-hand side pane click on "Secrets" then "Actions"
- Click on "New repository secret"
- Name: "API_TOKEN_GITHUB"
- Value: paste the token that you copied earlier
- name: Pushes to another repository
uses: meese-enterprises/github-action-push-to-another-repository@main
env:
SSH_DEPLOY_KEY: ${{ secrets.SSH_DEPLOY_KEY }}
API_TOKEN_GITHUB: ${{ secrets.API_TOKEN_GITHUB }}
with:
source-directories: |
frontend/client/doc
frontend/dialogs/doc
destination-directory-prefixes: |
client
dialogs
target-directory: src/api
destination-github-username: fake-username
destination-repository-name: fake-repository
user-email: fake@email.com
target-branch: main(you only need SSH_DEPLOY_KEY or API_TOKEN_GITHUB, depending on the method that you used)