Fork Repository
The first step to modify a repository is to fork it. Forking a repository creates a copy of the repository on your account.
Friendly Tip #1: For experimentation, fork or clone the public repository.
Create a Public Fork (Public Pieces)
Click the Fork button in the top right corner of the repository page (https://github.com/activepieces/activepieces)
Create a Private Fork (Private Pieces)
Private piece installation is available under the paid edition. You can still develop pieces, contribute them back, OR publish them to the public npm registry and use it in your own instance / project.
By following these steps, you can create a private fork on GitHub, GitLab or another platform and configure the “activepieces” repository as the upstream source, allowing you to incorporate changes from the “activepieces” repository.
- Clone the Repository:
Begin by creating a bare clone of the repository. Remember that this is a temporary step and will be deleted later.
- Create a Private Git Repository
Generate a new private repository on GitHub or your chosen platform. When initializing the new repository, do not include a README, license, or gitignore files. This precaution is essential to avoid merge conflicts when synchronizing your fork with the original repository.
- Mirror-Push to the Private Repository:
Mirror-push the bare clone you created earlier to your newly created “activepieces” repository. Make sure to replace <your_username> in the URL below with your actual GitHub username.
- Remove the Temporary Local Repository:
- Clone Your Private Repository:
Now, you can clone your “activepieces” repository onto your local machine into your desired directory.
- Add the Original Repository as a Remote:
If desired, you can add the original repository as a remote to fetch potential future changes. However, remember to disable push operations for this remote, as you are not permitted to push changes to it.
You can view a list of all your remotes using git remote -v. It should resemble the following:
When pushing changes, always use
git push origin.
Sync Your Fork
To retrieve changes from the “upstream” repository, fetch the remote and rebase your work on top of it.
Conflict resolution should not be necessary since you’ve only added pieces to your repository.
Fork Repository
The first step to modify a repository is to fork it. Forking a repository creates a copy of the repository on your account.
Friendly Tip #1: For experimentation, fork or clone the public repository.
Create a Public Fork (Public Pieces)
Click the Fork button in the top right corner of the repository page (https://github.com/activepieces/activepieces)
Create a Private Fork (Private Pieces)
Private piece installation is available under the paid edition. You can still develop pieces, contribute them back, OR publish them to the public npm registry and use it in your own instance / project.
By following these steps, you can create a private fork on GitHub, GitLab or another platform and configure the “activepieces” repository as the upstream source, allowing you to incorporate changes from the “activepieces” repository.
- Clone the Repository:
Begin by creating a bare clone of the repository. Remember that this is a temporary step and will be deleted later.
- Create a Private Git Repository
Generate a new private repository on GitHub or your chosen platform. When initializing the new repository, do not include a README, license, or gitignore files. This precaution is essential to avoid merge conflicts when synchronizing your fork with the original repository.
- Mirror-Push to the Private Repository:
Mirror-push the bare clone you created earlier to your newly created “activepieces” repository. Make sure to replace <your_username> in the URL below with your actual GitHub username.
- Remove the Temporary Local Repository:
- Clone Your Private Repository:
Now, you can clone your “activepieces” repository onto your local machine into your desired directory.
- Add the Original Repository as a Remote:
If desired, you can add the original repository as a remote to fetch potential future changes. However, remember to disable push operations for this remote, as you are not permitted to push changes to it.
You can view a list of all your remotes using git remote -v. It should resemble the following:
When pushing changes, always use
git push origin.
Sync Your Fork
To retrieve changes from the “upstream” repository, fetch the remote and rebase your work on top of it.
Conflict resolution should not be necessary since you’ve only added pieces to your repository.