gitignore sensitive files used for publishing releases #3266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
During the release process for GeoTrellis, I had to edit some files checked into the repo to add sensitive information. This runs the risk of accidentally committing these values into the tree, and always leaves tracked changes for my personal configuration in the
Makefile
.This PR moves them into template files and adds instructions for developers to copy them to the gitignored locations that are actually used by the release process. This way each dev can configure to their own desires and avoid dangerous operations.