Making my own fork of the client
-
Legacy or nextgen? If legacy, you could clone the repo, do your changes, and check the new commits every 2–3 days. Then, you can check if their changes conflict yours, and decide what to add.
-
To make your own fork of the client:
Clone the original repository to your local machine using Git.
Create a new branch for your fork to work on separate from the original.
Make changes to the codebase as desired, following best practices and adhering to any licensing requirements.
Test your changes thoroughly to ensure they function as intended.
Commit your changes to your branch and push them to your fork's remote repository.
Consider submitting a pull request to the original repository if you believe your changes would benefit the wider community.
Periodically sync your fork with the original repository to incorporate any upstream changes and maintain compatibility. -
To make your own fork of the client:
Clone the original repository to your local machine using Git.
Create a new branch for your fork to work on separate from the original.
Make changes to the codebase as desired, following best practices and adhering to any licensing requirements.
Test your changes thoroughly to ensure they function as intended.
Commit your changes to your branch and push them to your fork's remote repository.
Consider submitting a pull request to the original repository if you believe your changes would benefit the wider community.
Periodically sync your fork with the original repository to incorporate any upstream changes and maintain compatibility.
