Domain git-am.io
The Netherlands
-
Git configuration and history exposed
The following URL (usually
/.git/config) is publicly accessible and is leaking source code and repository configuration.First seen 2024-10-08 13:06
Last seen 2026-01-31 07:08
Open for 479 days-
Severity: medium
Fingerprint: 2580fa947178c88602b1737db148c044b81b03713d63bb82370a65225f8644e6[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = https://git.sr.ht/~sircmpwn/git-am.io fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master
Found on 2026-01-31 07:08262 Bytes
-
-
Open service 46.23.81.157:443 ยท git-am.io
2026-01-23 12:48
HTTP/1.1 200 OK Access-Control-Allow-Origin: * Access-Control-Request-Methods: GET, HEAD, OPTIONS Content-Length: 20528 Content-Security-Policy: default-src 'self' data: blob:; script-src 'self' 'unsafe-eval' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; worker-src 'self' 'unsafe-eval' 'unsafe-inline' data: blob:; frame-src https:; img-src data: https:; media-src https:; object-src 'none'; sandbox allow-downloads allow-forms allow-modals allow-pointer-lock allow-popups allow-presentation allow-same-origin allow-scripts; Content-Type: text/html; charset=utf-8 Last-Modified: Mon, 12 Aug 2024 13:31:34 GMT Vary: Accept-Encoding Date: Fri, 23 Jan 2026 12:48:51 GMT Connection: close Page title: Reviewing git contributions via email <!doctype html> <html> <head> <title>Reviewing git contributions via email</title> <link rel="stylesheet" type="text/css" href="index.css" /> <link rel="stylesheet" type="text/css" href="asciinema-player.css" /> <script src="asciinema-player.min.js"></script> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta charset="utf-8" /> </head> <body> <div class="container"> <h1>Reviewing git contributions via email</h1> <div class="intro"> <p> You may have read <a href="https://git-send-email.io">our interactive guide on sending patches with git send-email</a> and wondered — what does the other side of this workflow look like? This guide will introduce you to the tools and skills you need to efficiently review code via email. </p> <div class="alert"> <strong>Note:</strong> The tools and workflows maintainers use to manage this side of the git email workflow are much more diverse than the contributor side. This guide will teach you just one of many ways to approach the problem, and equip you with the tools and knowledge to develop your own personal workflow from this starting point. </div> <p> The git email workflow is powerful and flexible — it is used by the largest free software projects in the world to manage extremely high volumes of contributions effectively. Let's get you acquainted with the tools of the trade so you can dive right in. </p> </div> <footer> This guide brought to you courtesy of <a href="https://sourcehut.org">sourcehut</a>, the hacker's forge. 100% open source Git & Mercurial hosting, continuous integration, mailing lists, and <strong>no JavaScript</strong>! <a href="https://meta.sr.ht/register">Try it today</a>! </footer> <div class="intro" style="padding: 1rem 0"> <h3>Table of Contents</h3> <ol> <li><a href="#introduction">Introduction</a></li> <li><a href="#aerc">Introducing aerc</a></li> <li><a href="#sandbox">Preparing the sandbox</a></li> <li><a href="#reviewing-a-patch">Reviewing a patch</a></li> <li><a href="#applying-a-patch">Applying and testing a patch</a></li> <li><a href="#merge-conflicts">Dealing with merge conflicts</a></li> <li><a href="#advanced-aerc-usage">Advanced aerc usage</a></li> <li><a href="#resources">Further resources</a></li> </ol> </div> <div class="content"> <h2 id="introduction">Introduction</h2> <p> Reviewing code via email is one of the simplest, most efficient, and most scalable approaches to code review. It can also be one of the most intimidating to get started with. </p> <p> However, the crux of the workflow is simple: reviewing patches via email works the same way emails already work. You know how to use email — to review a patch you receive by email, you just reply to it with your feedback. There are some other tools we will familiarize you with, and some conventions and cultural norms to learn, but getting started with the basics is as easy as hitting "reply all". </p> <p> Ultimately, everyone's email workflow is a bit different. No two maintainers agree on the best approach, and many people use different email clients, tools, custom scripts, workflows, and conventions. We'll just get you situated with an easy way to start in this tutorial and you can learn more and build a workflow that suits your needs over time. And, to any established mail users reading along: we're all sure that <em>your</em> preferred workflow is much better than the one explained here — but we can't please everyFound 2026-01-23 by HttpPluginCreate report