I have a project (Swift but this applies to any project pretty much) and I end up using an API Key to make a call to OpenWeatherMap. I wanted to publish my repository without revealing my key. What's the best way to go about this so that I am able to both: hide my private API key (and instruct users to obtain their own in order to make the application work), and continue to work on the project using my own API key as seamlessly as possible.
Asked
Active
Viewed 55 times
1
-
It almost does, the linked question doesn't say what to do if I already have a project that I have made commits to that contains my API key in the history – Josh N Apr 27 '20 at 16:24
-
https://stackoverflow.com/search?q=%5Bgit%5D+remove+sensitive+file – phd Apr 27 '20 at 16:27
-
Yeah I think I'll just start with a new repo – Josh N Apr 27 '20 at 16:32