Скачать или смотреть A Simple Guide to Publish Merged Commits to a Remote Git Host Without Sharing Personal Information

Discover an efficient way to publish merged commits to a remote Git host while preserving your developers' privacy. Avoid sharing personal info and ensure only merged contributions reach the customer repository.
---
This video is based on the question https://stackoverflow.com/q/63359433/ asked by the user 'Mathias Bank' ( https://stackoverflow.com/u/322956/ ) and on the answer https://stackoverflow.com/a/63359552/ provided by the user 'eftshift0' ( https://stackoverflow.com/u/2437508/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: publish to remote host with merged commits

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Publishing Merged Commits to a Remote Git Host Without Sharing Personal Information

As a developer, managing multiple Git repositories can be tricky, especially when client requirements come into play. Many teams encounter the challenge of needing to push their code to a customer's Git server without exposing individual commit histories or personal developer information. If you find yourself in this position, you're not alone. Here's a streamlined approach to solve this problem effectively.

The Challenge

You are working on your own Git server and need to push completed code to a customer’s Git server. However, you wish to avoid sending detailed commit histories along with personal data of your developers. Instead, you want to publish only merged commits that summarize the individual changes made in your team.

Currently, you might be manually exporting files from your Git repository, copying them to a separate directory, and committing changes to the customer’s repository. While this can work, it's not efficient, and there’s a more automated solution using Git features that will make your life easier.

The Solution: Using an Orphan Branch for the Client

To achieve your goal of pushing merged commits without exposing user information, consider creating an orphan branch dedicated to the client. An orphan branch allows you to start a new branch with no history, meaning that it won't contain any personal or detailed commit histories from your team's work.

Step 1: Create the Orphan Branch

You’ll begin by creating an orphan branch at the point where you want to start integration with the client’s repository. Here’s how you can do it:

Checkout a new orphan branch: Start by creating a new orphan branch from the version where you want to begin. For instance, if you are starting from version v1.0.0:

[[See Video to Reveal this Text or Code Snippet]]

Make the first commit: Create a commit in this branch that signifies the first version for the client.

[[See Video to Reveal this Text or Code Snippet]]

At this point, the client branch contains a single commit that reflects the state of the project at v1.0.0, with no prior history or personal information attached.

Step 2: Pushing Changes to the Client Branch

As your project progresses and you release new versions, you’ll need to incorporate those changes into the client branch:

Checkout the new tag: When you release a new version, for example v1.1.0, you check out this version.

[[See Video to Reveal this Text or Code Snippet]]

Reset the client branch: Now, you want to stage the changes for the client branch:

[[See Video to Reveal this Text or Code Snippet]]

This command stages all differences between the current commit and the last commit in the client branch.

Commit the updates: You will now make a single commit that reflects the new changes made in the client branch:

[[See Video to Reveal this Text or Code Snippet]]

Update the branch: Make sure to point the client branch to the latest commit you just created:

[[See Video to Reveal this Text or Code Snippet]]

Push to the customer's repository: Finally, you can push the client branch to the customer's Git repository:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By following this structured approach using an orphan branch, you can effectively push merged commits to your client’s Git server without exposing your developers' personal information. This ensures a cleaner and more professional collaboration while maintaining the integrity of your team's contributions.

Take the time to implement this method in your workflow, and you'll discover the benefits of better version control practices while mee