Added repo #1
Merged
Added repo #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
iverestefans
approved these changes
Jun 10, 2021
fredx30
approved these changes
Jun 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No, your eyes are not deceiving. This is a new PR with the same ID...
Our k8s cluster secret was accidentally pushed. Of all the secrets one could place in the repo... To be sure it's gone I recreated the repo, as that forces a clear of the git history, where force pushes still leave the original commits up for a short while.
Got an email from GitGuardian (https://gitguardian.com) that they detected our k8s secret. We don't even use GitGuardian, but it's their way of marketing. Quite clever.
But then the question remains, who else listened to GitHub events? Probably a lot of people.
We have to regenerate the secret. It's too risky to leave it be. Even though it's hidden under a private network.
For this PR, which closes iver-wharf/iver-wharf.github.io#32, the following changes were made: