Skip to main content

Github–Secret scanning

One of the things you certainly want to avoid as a developer is accidently checking in secrets(passwords, api keys, ...) in your code repository. Such a credential leak can have severe consequences and is something you certainly want to avoid.

If you are using GitHub as your source repository and you have a public repository, I have some good news for you. Since December last year, Github made secret scanning available for free  for all public repositories.

It is not enabled out-of-the-box but easy to configure and get up and running for you repo. Let me show you...

Enable Secret scanning for your public Github repository.

  • Browse to your public repository in Github and click on the Security tab.

  • Click on Secret Scanning on the Security page.

  • Click on the link to the Repository settings to bring you to the correct setting on the Settings page.
  • At the bottom of the page, click on the Enable button in the Secret scanning section.

  • That’s it!

Now every time when you push a commit to this repository, Github will scan the content of those commits for secrets. If secret scanning detects a secret, GitHub generates an alert that is send to the repository administrators and organization owners..

You can also check if secrets are found in the following way:

  • Go back to the Security page and click on Secret Scanning on the left or bView Detected Secrets.

  • On the Secret Scanning page, you can see any secret that is detected.

More information: About secret scanning - GitHub Docs

Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should