<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tracking on Saksham Anand</title>
    <link>/tags/tracking/</link>
    <description>Recent content in Tracking on Saksham Anand</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 22 Apr 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/tracking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tracking via GitHub Keys</title>
      <link>/blog/github-keys-tracking/</link>
      <pubDate>Sat, 22 Apr 2023 00:00:00 +0000</pubDate>
      <guid>/blog/github-keys-tracking/</guid>
      <description>Have you ever been in a situation where you are managing a large number of users and one of them has committed sensitive information to a repository on GitHub? The issue is exaggerated even more when the username is ambiguous, the .patch file does not have any helpful information and generally, no solid details are present to find out who made the commit.
Depending on how your organisation works, you may be able to use .</description>
    </item>
  </channel>
</rss>
