# GitHub Issues GitHub's integrated issue-tracking tool for planning, discussing, and tracking repository work. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Visual Studio Code 1.137 DevFeed: [Visual Studio Code 1.137]() Original publisher: [Read original article]() Author: Visual Studio Code Team Published: 2026-09-09T17:00:00Z Content type: release Language: en Sources: [Visual Studio Code - Code Editing. Redefined.]() Topics: [vs-code](), [Automation](), [GitHub](), [GitHub Issues](), [Pull Request](), [GitHub Copilot]() Tags: [2026](), [article](), [automation](), [experimental](), [github](), [github-issues](), [pull-request](), [release](), [updates](), [visual-studio](), [voice](), [vs-code]() ### AI overview Visual Studio Code 1.137 introduces scheduled automations, experimental voice interaction with agents, workspace-attached quick chats, and GitHub issues and pull request details in the Agents window. ### Source excerpt Learn what's new in Visual Studio Code 1.137 Read the full article ## How we closed 1,500 GitHub issues in one month DevFeed: [How we closed 1,500 GitHub issues in one month]() Original publisher: [Read original article]() Author: Marcos Hernanz Published: 2026-09-04T04:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [GitHub Issues](), [Next.js](), [AI-assisted coding](), [issue tracker](), [Maintainers](), [bug]() Tags: [agent](), [ai](), [bug](), [github-issues](), [issue-tracker](), [maintainers](), [next-js](), [sandbox](), [vercel]() ### AI overview The Next.js team describes using an AI research agent to help maintainers review an issue backlog, close outdated reports, and retain issues that still matter. ### Source excerpt How the Next.js team used an agent to research old reports and work through the issue backlog. ## Automating quality support at scale: AI and human in the loop DevFeed: [Automating quality support at scale: AI and human in the loop]() Original publisher: [Read original article]() Author: Hugo Casademont Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [Windmill Blog]() Topics: [Artificial Intelligence](), [Claude](), [Discord](), [Slack](), [GitHub Issues](), [email](), [Linear](), [telemetry](), [WebSocket]() Tags: [ai](), [ai-windmill-support-claude](), [automated](), [claude](), [discord](), [email](), [github-issues](), [linear](), [slack](), [support](), [telemetry](), [windmill]() ### AI overview Windmill describes an internal support-automation pipeline that consolidates Discord, Slack, email, and GitHub issues into a Discord queue. It uses Claude and customer context to triage requests, draft replies and fixes, while requiring human approval before responses are sent. ### Source excerpt How does Windmill automate its own support? A Windmill pipeline funnels Discord, Slack and email tickets into one Discord queue, triages them with Claude, drafts replies, and dispatches fixes. ## Bugs, feature requests, career stories, and weekly readings 💡 DevFeed: [Bugs, feature requests, career stories, and weekly readings 💡]() Original publisher: [Read original article]() Author: Luca Rossi Published: 2026-08-03T07:01:44Z Content type: article Language: en Sources: [Refactoring]() Topics: [GitHub Issues](), [GitHub](), [Open Source](), [Artificial Intelligence]() Tags: [ai](), [bugs](), [career-stories](), [feature](), [github](), [github-issues](), [open-source](), [weekly]() ### AI overview This Monday Ideas newsletter discusses separating bugs from feature requests in product feedback workflows. It recommends routing submissions to the appropriate channels, deduplicating entries, and using intake workflows to turn valid work into tasks. It also includes career interview advice and a sponsored section about AI productivity and context. ### Source excerpt Monday Ideas -- Edition #219 ## Examples of Agent Goals, Loops, and Scheduled Workflows in Codex and Claude Code DevFeed: [Examples of Agent Goals, Loops, and Scheduled Workflows in Codex and Claude Code]() Original publisher: [Read original article]() Author: Owain Lewis Published: 2026-07-02T07:01:00Z Content type: article Language: en Sources: [The AI Engineer]() Topics: [codex](), [Loop Engineering](), [Automation](), [Claude Code](), [Pull Request](), [GitHub Issues](), [ci]() Tags: [agent](), [ai-agents](), [automation](), [ci](), [claude-code](), [codex](), [github-issues](), [logs](), [review](), [scheduled](), [tests](), [workflow]() ### AI overview The article explains how prompts, goals, recurring runs, and workflows differ, then presents examples of using agents for recurring engineering tasks. It emphasizes evidence, stop rules, tests, CI, logs, issues, pull requests, and human review as safeguards because agents can misunderstand context or make mistakes. ### Source excerpt Practical ways to combine prompts, goals, and scheduled runs in Codex and Claude Code. ## Seamless Crash Protection That Symbolicates Native Crashes DevFeed: [Seamless Crash Protection That Symbolicates Native Crashes]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-22T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [App](), [GitHub Issues](), [Cloud](), [Disk image](), [Android](), [iOS](), [Linux](), [macOS](), [Windows](), [tvOS](), [watchOS]() Tags: [android](), [cloud](), [crash](), [data](), [github-issues](), [ios](), [linux](), [macos](), [native](), [protection](), [retry](), [storage](), [watchos](), [win32](), [windows]() ### AI overview The article describes the new com.codename1.crash client, which captures crashes on devices, removes personal data before transmission, stores reports until upload succeeds, retries failed uploads, and uses cloud-side symbolication to file deduplicated reports as GitHub issues. It covers native crash support across multiple platforms and deobfuscation of Android exceptions. ### Source excerpt The new com.codename1.crash client captures crashes on device, scrubs personal data before anything is sent, retries reliably through a storage-first queue, and lets the build cloud symbolicate native crashes and file them as GitHub issues instead of emails. ## Native Linux, Apple Watch, A Game Builder And Crash Protection DevFeed: [Native Linux, Apple Watch, A Game Builder And Crash Protection]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-19T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Linux](), [watchOS](), [GitHub Issues](), [Java](), [Kotlin](), [Programming]() Tags: [api](), [apple](), [apple-watch](), [crash](), [desktop](), [gaming](), [github-issues](), [java](), [kotlin](), [linux](), [native](), [watchos]() ### AI overview This weekly Codename One update describes a native Linux desktop port, Apple Watch and Wear OS support, a visual Game Builder with a high-level gaming API, and crash protection that symbolicates native crashes and files them as GitHub issues. It also notes a rebuild of the build cloud and related failed builds. ### Source excerpt This week adds a native Linux desktop port, an Apple Watch and Wear OS port, a visual Game Builder with a high-level gaming API, and seamless crash protection that symbolicates native crashes and files them as GitHub issues. ## How I'm building autonomous agent loops DevFeed: [How I'm building autonomous agent loops]() Original publisher: [Read original article]() Author: Owain Lewis Published: 2026-06-13T14:02:17Z Content type: tutorial Language: en Sources: [The AI Engineer]() Topics: [Loop Engineering](), [Artificial Intelligence](), [GitHub Issues](), [Claude Code](), [codex](), [GitHub]() Tags: [agent](), [ai](), [autonomous](), [claude-code](), [codex](), [github-issues](), [loops](), [workflow]() ### AI overview This guide explains how to build autonomous agent loops in which agents read project state, perform work, update that state, and repeat on a schedule or in response to events. It presents GitHub Issues as a control plane and describes manager and worker loops built with Claude Code and Codex, including risk classification, ticket management, and safeguards against destructive actions. ### Source excerpt A guide on loop engineering and autonomous AI loops ## From latency to instant: Modernizing GitHub Issues navigation performance DevFeed: [From latency to instant: Modernizing GitHub Issues navigation performance]() Original publisher: [Read original article]() Author: Natalie Guevara Published: 2026-05-14T16:00:00Z Content type: article Language: en Sources: [GitHub]() Topics: [GitHub Issues](), [Latency](), [Caching](), [client](), [Web]() Tags: [architecture](), [architecture-optimization](), [caching](), [engineering](), [github](), [github-issues](), [latency](), [local](), [performance](), [web-performance]() ### AI overview The GitHub Issues team describes how it improved navigation performance by moving work to the client, rendering from locally cached data, and revalidating in the background. The approach uses IndexedDB, preheating, and a service worker to reduce perceived latency, while acknowledging implementation tradeoffs. ### Source excerpt How the GitHub Issues team used client-side caching, smart prefetching, and service workers to make navigation feel instant. The post From latency to instant: Modernizing GitHub Issues navigation performance appeared first on The GitHub Blog. ## Podman Standups! DevFeed: [Podman Standups!]() Original publisher: [Read original article]() Author: tsweeney Published: 2026-05-01T17:21:55Z Content type: article Language: en Sources: [blog.podman.io]() Topics: [podman](), [GitHub Issues]() Tags: [2026](), [cncf](), [community](), [events](), [github-issues](), [podman](), [red-hat](), [team](), [uncategorized](), [video]() ### AI overview The Podman project is moving its recurring standup meetings to the CNCF calendar so the wider community can join. Meetings will occur on Mondays and Thursdays, beginning May 4, 2026, with status roundtables followed by optional discussion topics. The existing Podman Community Cabal meeting will end after May 5, 2026. ### Source excerpt The standups are coming, the standups are coming! Come one, come all to the Podman Standup Meetings! For the past many years, the Podman team at Red Hat has held standup meetings on Mondays at 10:00 a.m. Eastern, and also on Thursdays at 11:00 a.m. Eastern. (Currently UTC-4, then UTC-5 once the USA goes to [...] ## Qinglong task scheduler RCE vulnerabilities exploited in the wild for cryptomining DevFeed: [Qinglong task scheduler RCE vulnerabilities exploited in the wild for cryptomining]() Original publisher: [Read original article]() Author: Julia Kinday Published: 2026-04-27T00:00:00Z Content type: news Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Vulnerabilities](), [incident](), [Security](), [Express](), [GitHub Issues](), [Docker](), [GitHub](), [Open Source](), [Server](), [Shell](), [JavaScript](), [npm]() Tags: [application-security](), [attacks](), [auth](), [authentication](), [awareness](), [blog](), [ci-cd](), [cloud](), [cloud-security](), [code](), [developer](), [devops](), [docker](), [enablement](), [github](), [github-issues](), [incident](), [javascript](), [malware](), [node-js](), [open-source](), [open-source-security](), [routing](), [security](), [security-labs](), [self-hosted](), [servers](), [snyk-code](), [snyk-container](), [snyk-learn](), [snyk-open-source](), [snyk-security-intel](), [tech](), [typescript](), [vulnerabilities](), [vulnerability]() ### AI overview Qinglong, an open-source self-hosted task scheduling panel, was exploited through two authentication bypass vulnerabilities affecting versions 2.20.1 and earlier. Attackers used unauthenticated remote code execution to deploy cryptocurrency miners on publicly accessible installations. The article describes the vulnerabilities, their Express.js routing and middleware flaws, and the impact on operators using cloud VPS instances and home servers. ### Source excerpt Two authentication bypass vulnerabilities (CVE-2026-3965, CVE-2026-4047) in the Qinglong task scheduling panel were exploited in the wild to deploy cryptomining malware. Here's what happened, how the attacks worked, and what self-hosted application operators should learn from this incident. ## Behind the Scenes: How Maintaining Cloud Native Buildpacks Powers Platforms Like Heroku DevFeed: [Behind the Scenes: How Maintaining Cloud Native Buildpacks Powers Platforms Like Heroku]() Original publisher: [Read original article]() Author: Juan Bustamante Published: 2026-03-17T15:00:03Z Content type: opinion Language: en Sources: [Heroku]() Topics: [Heroku](), [Maintainers](), [Cloud Native Ecosystem](), [Command-line interface](), [releases](), [Security](), [vulnerability](), [GitHub Actions](), [GitHub](), [GitHub Issues](), [Google Cloud Platform (GCP)](), [Docker]() Tags: [buildpacks](), [cli](), [cloud](), [cloud-infrastructure](), [cloud-native](), [cloud-native-ecosystem](), [docker](), [ecosystem](), [engineering](), [github](), [github-actions](), [github-issues](), [google-cloud](), [google-cloud-run](), [heroku](), [maintainers](), [maintenance](), [open-source](), [patches](), [platform](), [releases](), [security](), [vulnerability]() ### AI overview This article describes how pack CLI maintainers support Cloud Native Buildpacks through releases, security patches, issue triage, pull request reviews, CI changes, and feature development. It explains how Heroku-funded maintenance benefits Heroku, Google Cloud Run, and internal platform teams. ### Source excerpt Most developers never see the 11 pack releases we shipped in the last 14 months as pack CLI maintainers. That's actually a good sign--it means the infrastructure just works. When a critical vulnerability emerges requiring an immediate upgrade, the fix is shipped within days. Here's what most developers don't see: that same security patch now [...] The post Behind the Scenes: How Maintaining Cloud Native Buildpacks Powers Platforms Like Heroku appeared first on Heroku. ## How I Built an Autonomous Development System with AI Agents DevFeed: [How I Built an Autonomous Development System with AI Agents]() Original publisher: [Read original article]() Published: 2026-02-16T14:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Android](), [Loop Engineering](), [Development](), [GitHub Issues](), [codex](), [Next.js](), [PostgreSQL](), [Prisma](), [Redis]() Tags: [agents](), [ai](), [automation](), [codex](), [development](), [github-issues](), [next-js](), [postgresql](), [prisma](), [redis](), [security]() ### AI overview The author describes an autonomous development system for the Learnfolx training platform. Specialized scanners identify problems and create GitHub issues, a triage process prioritizes them, and an executor implements fixes and closes issues. Smoke tests provide periodic verification. The system uses Codex App automations and an external cron, with reported results including 80 issues created and about 50 closed in three days. ### Source excerpt Everything Android, Kotlin and other random topics ## I've created a website to track the team's activity DevFeed: [I've created a website to track the team's activity]() Original publisher: [Read original article]() Author: Alexey Milovidov Published: 2025-11-10T00:00:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [GitHub Issues](), [Database](), [Bun](), [elasticsearch](), [PyTorch](), [Chromium]() Tags: [clickhouse](), [database](), [developer-productivity](), [github](), [github-issues](), [metrics](), [pull-requests](), [sql]() ### AI overview The article introduces a website for comparing GitHub repository activity metrics and argues that commits, pull requests, and issue counts should be interpreted as secondary signals rather than productivity targets. ### Source excerpt Initially, I wanted to make a single report to incentivise for looking at and resolving GitHub issues. But I'm greedy, so in the end it appeared to be a website where you can compare various metrics on team activities across GitHub repositories. ## Devstral DevFeed: [Devstral]() Original publisher: [Read original article]() Published: 2025-05-21T12:00:00Z Content type: release Language: en Sources: [Mistral AI Blog]() Topics: [AI-assisted coding](), [Large Language Model](), [Benchmark](), [Open Source](), [GitHub Issues](), [Deployment](), [Security](), [Software Engineering]() Tags: [agentic-coding](), [ai](), [benchmark](), [github-issues](), [llm](), [local](), [models](), [open](), [open-source](), [security]() ### AI overview Mistral AI and All Hands AI introduce Devstral, an Apache 2.0-licensed agentic LLM for software engineering. The article reports a 46.8% score on SWE-Bench Verified, says Devstral outperforms prior open-source models and several larger or closed models, and describes local, on-device, enterprise, and agentic coding use cases. ### Source excerpt The most powerful AI platform for enterprises. Customize, fine-tune, and deploy AI assistants, autonomous agents, and multimodal AI with open models. ## Chromium Issue Tracker migration is complete DevFeed: [Chromium Issue Tracker migration is complete]() Original publisher: [Read original article]() Author: Chromium Blog (noreply@blogger.com) Published: 2024-02-05T16:42:00Z Content type: news Language: en Sources: [Chromium Blog]() Topics: [Chromium](), [GitHub Issues](), [migration](), [Google](), [Tooling](), [Open Source](), [Documentation](), [Git]() Tags: [chromium](), [documentation](), [ecosystem](), [git](), [google](), [issue-tracker](), [migration](), [none](), [open-source](), [tooling]() ### AI overview Chromium has completed its migration from Monorail to the Chromium Issue Tracker, powered by Google Issue Tracker. Existing Monorail links will redirect to the migrated issues, and feedback will help improve the new tracker experience. ### Source excerpt We are thrilled to share that Chromium issue tracking has migrated! Access the Issue Tracker, and supporting documentation. Why was this done Issue tracking moved from Monorail to the Chromium Issue Tracker (powered by the Google Issue Tracker) to provide a feature-rich and well-supported issue tracker for Chromium's ecosystem. Chromium joins other open source projects (Git, Gerrit) on this tooling. What happens moving forward Existing Monorail issue links will redirect to the migrated issues in the new issue tracker. We will prioritize feedback to continue to improve the issue tracker experience. Help & Feedback You can reach out at any time to issue-tracker-support@chromium.org with questions or concerns. ## Mintlify Launch Week Recap: CLI, Docs Feedback, Global CSS, API Playground, and Web Editor DevFeed: [Mintlify Launch Week Recap: CLI, Docs Feedback, Global CSS, API Playground, and Web Editor]() Original publisher: [Read original article]() Author: Han Wang Published: 2023-10-02T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Command-line interface](), [Documentation](), [Web Development](), [CSS](), [GitHub](), [GitHub Issues]() Tags: [announcements](), [cli](), [css](), [documentation](), [github](), [github-issues](), [hot-reloading]() ### AI overview The article recaps five Mintlify features released during Launch Week: CLI enhancements, Docs Feedback, Global CSS, a redesigned API Playground, and a Web Editor. It highlights CLI size and installation-time reductions, feedback and analytics capabilities, design customization, and browser-based editing with live preview. ### Source excerpt Last week, we launched a feature a day, from CLI enhancements to Global CSS to the Web Editor. ## New Keycloak maintainer: Alexander Schwartz DevFeed: [New Keycloak maintainer: Alexander Schwartz]() Original publisher: [Read original article]() Author: Bruno Oliveira Published: 2023-06-27T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Benchmark](), [Documentation](), [GitHub](), [GitHub Issues](), [pull-requests]() Tags: [benchmark](), [bug-fixes](), [documentation](), [github](), [github-issues](), [idm](), [kerberos](), [keycloak](), [ldap](), [new-features](), [openid-connect](), [pull-requests](), [saml](), [sso]() ### AI overview Keycloak announces Alexander Schwartz as an official maintainer, highlighting his contributions to the project, including work on its store, documentation, benchmark project, community discussions, pull requests, features, bug fixes, and issue triage. ### Source excerpt We're delighted to announce Alexander Schwartz as an official maintainer of Keycloak. Alexander started contributing to Keycloak in 2015. He applied it in several customer installations and is maintaining the Dropwizard module for Keycloak. In January 2022, he joined Red Hat. Since then, he has contributed to Keycloak's store and documentation and is the key contributor to the Keycloak benchmark project. He helped with Keycloak's submission to CNCF, and represented Keycloak at KubeCon Amsterdam in April 2023. He has shown his commitment to the Keycloak community by collaborating on design discussions, participating in GitHub discussions, reviewing pull-requests, answering questions on the Keycloak mailing lists, contributing to new features, bug fixes and triaging GitHub issues. The Keycloak team is very excited to welcome Alexander as our new maintainer and long-time contributor. ## How to setup comments on your static blog DevFeed: [How to setup comments on your static blog]() Original publisher: [Read original article]() Published: 2023-05-30T00:00:00Z Content type: tutorial Language: en Sources: [Arkadiusz Chmura]() Topics: [GitHub Issues](), [Website](), [Hugo](), [Open Source](), [User Experience]() Tags: [code](), [database](), [github](), [github-issues](), [how-to](), [hugo](), [open-source](), [setup](), [static](), [user-experience](), [website]() ### AI overview This tutorial explains how to add utterances comments to a static blog using GitHub Issues as comment storage. It covers repository setup, widget configuration, script integration, and handling the widget theme for dark mode. ### Source excerpt With a tool called utterances, it's very easy to add comments to your website with minimal code and no need for a database. ## Implementing the Auto-refreshing Official Kubernetes CVE Feed DevFeed: [Implementing the Auto-refreshing Official Kubernetes CVE Feed]() Original publisher: [Read original article]() Author: The Kubernetes Authors Published: 2022-09-12T00:00:00Z Content type: article Language: en Sources: [Kubernetes Contributors Blog]() Topics: [Kubernetes](), [Vulnerabilities](), [GitHub Issues](), [GitHub](), [REST API](), [Google Cloud Platform (GCP)](), [JSON Feed](), [Netlify](), [Markdown]() Tags: [cve](), [github](), [github-issues](), [google-cloud](), [json](), [kubernetes](), [markdown](), [netlify](), [rest-api](), [security]() ### AI overview This article explains how Kubernetes implemented an official, auto-refreshing CVE feed. The system identifies relevant GitHub Issues, periodically retrieves them through the GitHub REST API, stores the data in a Google Cloud Bucket, and publishes JSON Feed and Markdown representations. ### Source excerpt Author: Pushkar Joglekar (VMware) Accompanying the release of Kubernetes v1.25, we announced availability of an official CVE feed as an alpha feature. This blog will cover how we implemented this feature. Implementation Details An auto-refreshing CVE feed allows users and implementers to programmatically fetch the list of CVEs announced by the Kubernetes SRC (Security Response Committee). To ensure freshness and minimal maintainer overhead, the feed updates automatically by fetching the CVE related information from the CVE announcement GitHub Issues. Creating these issues is already part of the existing Security Response Committee (SRC) workflow. Pre-requisites Until December 2021, it was not possible to filter for issues or PRs that are tied to CVEs announced by Kubernetes SRC. We added a new label, official-cve-feed to address that, and SIG-Security labelled relevant issues with it. The in-scope issues are closed issues for which there is a CVE ID(s) and is officially announced as a Kubernetes security vulnerability by SRC. You can now filter on all of these issues and find them here . For future security vulnerabilities, we added the label to the SRC playbook so that all the future in-scope issues will automatically have this label. Building on existing tooling For the next step, we created a prow job in order to periodically query the GitHub REST API and pull the relevant issues. The job runs every two hours and pushes the CVE related information fetched from GitHub into a Google Cloud Bucket. For every website build (at least twice a day), Netlify data templates make a call to this Google Cloud Bucket to pull the CVE information and then parses into fields that are JSON Feed v1.1 compliant. The JSON file is available for programmatic consumption by automated security tools. For humans, the JSON also gets transformed into a Markdown table for easy viewing. Design Considerations Building trust and ensuring that the feed is not stale were our main priorities when ## Tasks Of Affirmation: A New Twitch Live Stream Series DevFeed: [Tasks Of Affirmation: A New Twitch Live Stream Series]() Original publisher: [Read original article]() Author: Adam McNeilly Published: 2021-09-02T00:00:00Z Content type: article Language: en Sources: [Android Essence]() Topics: [To-Do](), [Twitch](), [Streaming](), [android-development](), [GitHub Issues](), [GitHub]() Tags: [android](), [android-development](), [github](), [github-issues](), [streaming](), [twitch]() ### AI overview The author announces a new Twitch live-stream series, Tasks Of Affirmation, focused on building a more supportive and compassionate to-do list application. The streams will document Android development in real time, including learning, debugging, and project organization with GitHub Projects and GitHub Issues. ### Source excerpt In the late summer of 2020, I began live streaming on my Twitch channel. We started off by building an Android Study Guide application. The purpose of the application was to build something people would be interested in using, while also taking the opportunity to build an application out in the open. For a number of reasons, discussed in the latest video, I've decided to sunset that project and begin a new live stream series: Tasks Of Affirmation. ## Temporal Transparency Update #2 DevFeed: [Temporal Transparency Update #2]() Original publisher: [Read original article]() Author: Ryland Goldstein Published: 2020-07-18T04:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [Code](), [GitHub](), [GitHub Issues]() Tags: [github](), [github-issues](), [product-news](), [progress](), [release](), [transparency](), [update]() ### AI overview Temporal's second V1 status update says the July 31, 2020 code-completion date remains unchanged. The team added tasks from open issues in public GitHub repositories, prioritized the remaining work, and expected many in-progress items to be completed that week. ### Source excerpt Hope everyone is having a great Friday. I'm happy to share our second V1 status update as part of our continued effort to be more transparent. ## covidnearme.org: A local COVID-19 case-tracking website DevFeed: [covidnearme.org: A local COVID-19 case-tracking website]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-03-13T00:00:00Z Content type: release Language: en Sources: [Scott Johnson]() Topics: [Website](), [data](), [GitHub Issues](), [issue tracker]() Tags: [announce](), [covid](), [covid-19](), [covidnearme](), [covidnearme-org](), [data](), [github-issues](), [issue](), [tool](), [web]() ### AI overview The article announces covidnearme.org, a website intended to help users view local COVID-19 case information, bookmark locations, and see a leaderboard of cases. It also describes plans to track metrics such as deaths and recoveries and report bugs through GitHub Issues. ### Source excerpt I'd like to say that I'm happy to announce: https://www.covidnearme.org/ but I'm not. Like a lot of us, nay, most of us, I find the current COVID-19 / Corona virus bothersome if not scary. But the world is what it is and we are better off knowing more about COVID-19 rather than less so I made a tool. What is covidnearme.org? Covnearme.org is a web site which lets you: Easily drill down to where you live. Bookmark a location or location that you care about See a leaderboard of cases BUT WHAT HAPPENED IN THE US ON 3/10? That is apparently the date when Johns Hopkins stopped reporting US level county data and only data at the state level. Yes that means that the US is officially LESS OPEN than China. Let's compare a screenshot between Seattle and Hubei: If you think this is the same bull crap that we do then please use this hashtag when you tweet: #hopkinswheresmylocaldata #Covid_19 Where's the Damn Map? We didn't put one in (yet). I've been using the Hopkins tracker for several weeks now and it gives me a great feel for the global scene but I don't just want global - I want local. And I'm too damn fat fingered to make their map work for me easily. Why Did You Build This? We wanted: The ability to know what's happening near the people we love. The ability to bookmark a location - our homes, our parent's homes, our friends workplaces The ability to know metrics which people aren't posting yet like the death metrics (why the hell is Italy so much higher?) and the recovery metrics (Seattle has a lot of cases but the recovery percentages are pretty good) How Do I Give You Bugs? We have setup a public github repo for this to capture bugs as github issues. Just file an issue and please, please, please give us the url to where you have issues. Goto: https://github.com/fuzzygroup/covdidnearme_bugs/issues Note: If anyone out there in the bug tracking world wants to give us tooling for bugs, contact fuzzygroup at gmail.com Who the Hell Are You? You keep saying we. Who is we? The ## When You Forget Your Branch Name Use Git Reflog DevFeed: [When You Forget Your Branch Name Use Git Reflog]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2019-11-25T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Git](), [version-control](), [GitHub Issues](), [Pull Request](), [ci]() Tags: [cmn](), [command](), [commit](), [git](), [github](), [github-issues](), [pull-request](), [version-control]() ### AI overview This article explains how Git reflog can help recover the name of a branch that was forgotten in a workflow using issue branches, pull requests, and separate master and develop branches. The author uses reflog output, including local dates, to identify the branch and resume work. ### Source excerpt For my current side project, cmn, I'm using a version control model of issue branches as described here back in June (about when I started this). Basically the model is: The master branch is always pristine and always deployable. The develop branch takes changes from issue branches and is then merged into master by a CI server. Anything you work on, no matter how small, gets a github issue and goes thru a pull request approach. I've never been a real big fan of structured engineering approaches and my last boss, Taylor Williams, did a fantastic job of teaching us this and - he was right. Even on a small side project, there are definite benefits to solid, well defined workflow processes. One disadvantage when you work this way is that you end up with a lot of branches. And since branches tend to be named for the issue, it isn't always apparent the difference between say 444 and 445. When branches are transitory such as "fix this bug", that isn't a big deal. But when a branch is longer lived, because it just can't be completed in a short period of time, you are likely to simply forget the branch name. As an example, last Thursday night, I started work on a pretty complex enhancement and then a new bug came up Friday morning. My response was to do an add / commit and then change back to develop and create a new issue and fix that bug. And, somehow, between Friday morning and tonight, Monday night, the issue number has jumped by 30 issues (if you work this way then you make a lot of issues). So I went to find the branch and I simply couldn't. I was at 480 and I looked back at the Github Issues page and I thought it might have been 460 but that turned out not to be it. As I thought about it, I realized that I knew when I last worked on it, the preceding Thursday, and there had to be a way to to look at branches by date created. A bit of Internet research led me to the git reflog command: git reflog --date=local Here is an example of reflog's output: e95bf81 HEAD@{Fri Nov [Next page]()