I developed a mail client, and the SMTP gateway has an authentication identifier and password, which is in the code. Now I want to pass them to the hero, but not github. The project has several employees. So, I can create a new branch and save the keys there and deploy it to the hero. This branch remains only locally and does not reach github. However, if I follow this method, then all employees need to maintain a local branch for the hero and always follow the following deployment procedure: 1. make changes to the master 2. Merge the main and heroin branches 3. Expand the hero
It seems error prone and repetitive. Not elegant.
Another way I came up with is to commit with authentication values, click on the hero, and then return the commit. However, I think the authentication values will still have github value if I do this. Even if github does not have authentication values, this must be done every time a co-author pushes any new function.
Please offer.
source
share