# also Published articles for also. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Migrating to a Mobile Monorepo for React Native DevFeed: [Migrating to a Mobile Monorepo for React Native]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-05-29T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [monorepo](), [React Native](), [Mobile](), [Submodules](), [Android](), [iOS](), [pull-requests](), [Jenkins]() Tags: [also](), [android](), [engineering](), [ios](), [jenkins](), [mobile](), [monorepo](), [news](), [react-native](), [submodules]() ### AI overview Khan Academy describes moving its React Native-related iOS and Android repositories from separate repositories and submodules into a single mobile monorepo. The change was intended to reduce synchronization problems, coordinate bridge changes across platforms, make pull requests and reviews more coherent, and simplify verification between codebases. The article also outlines repository-merging steps and anticipated trade-offs. ### Source excerpt By Jared Forsyth Over the past few months, we've been adding some React Native to our existing iOS ... Read more ## From alert to resolution: Manage incidents with Bits Chat in Slack DevFeed: [From alert to resolution: Manage incidents with Bits Chat in Slack]() Original publisher: [Read original article]() Author: Nancy Zhu; Evan Marcantonio; Nicole Parisi; Chris Miller Published: 2026-09-16T00:00:00Z Content type: tutorial Language: en Sources: [Datadog | The Monitor blog]() Topics: [incident](), [Slack](), [Artificial Intelligence](), [telemetry](), [Code](), [Pull Request]() Tags: [ai](), [also](), [bits-ai](), [code](), [collaboration](), [ecommerce](), [incident](), [monitor](), [root-cause-analysis](), [slack](), [telemetry]() ### AI overview This tutorial explains how Bits Chat in Slack can support incident response by investigating alerts, analyzing telemetry, coordinating responders, generating a pull request for a fix, and tracking follow-up work within the incident channel. ### Source excerpt Use Bits Chat in Slack to investigate incidents, collaborate with responders, make code fixes, and capture follow-up work where your team communicates. ## Code review comments are the rules you forgot to write down DevFeed: [Code review comments are the rules you forgot to write down]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2026-07-27T00:00:00Z Content type: article Language: en Sources: [Posts on Marco Gomiero]() Topics: [Code review](), [Pull Request](), [Loop Engineering](), [context](), [Markdown]() Tags: [agent](), [ai-agents](), [also](), [code-review](), [maintenance](), [markdown](), [workflow]() ### AI overview The article describes a workflow for using AI agents to inspect recent pull-request review comments, identify recurring violations of project conventions, and propose updates to instruction files such as AGENTS.md. It presents code-review feedback as evidence of undocumented project rules and discusses using scripts to retrieve review comments. ### Source excerpt If you work with AI agents, you have an instruction file (and if you don't, you should!) usually called AGENTS.md (with CLAUDE.md symlinked to it, because standards are hard to follow). This Markdown file is automatically added to the AI context, and it should contain all the guidelines for the project and everything that the agent should be aware of. For example, how to build the project, styling, conventions, and anything else that should be known to achieve the best possible result. ## How Codex coordinates parallel coding tasks through a coordinator thread DevFeed: [How Codex coordinates parallel coding tasks through a coordinator thread]() Original publisher: [Read original article]() Author: Owain Lewis Published: 2026-06-06T12:54:48Z Content type: article Language: en Sources: [The AI Engineer]() Topics: [codex](), [ai-coding](), [Git](), [Pull Request](), [NEO]() Tags: [ai-agents](), [ai-coding](), [also](), [codex](), [git]() ### AI overview The article describes using a Codex coordinator thread to create and manage multiple worker threads for parallel coding tasks. Each worker uses a separate Git branch and worktree, follows an implementation and testing workflow, receives review feedback, and opens a draft pull request. ### Source excerpt How I let OpenAI Codex run a team of AI agents from a single Codex coordinator thread. ## The Engineer's Guide to AI-Assisted Productivity DevFeed: [The Engineer's Guide to AI-Assisted Productivity]() Original publisher: [Read original article]() Author: Alex Razvant Published: 2026-02-12T12:01:56Z Content type: article Language: en Sources: [Neural Bits]() Topics: [Artificial Intelligence](), [code productivity](), [coding](), [Pull Request](), [Claude Code](), [cursor](), [hooks](), [Obsidian]() Tags: [agent](), [ai](), [also](), [article](), [claude](), [claude-code](), [code](), [cursor](), [developer-productivity](), [guide](), [hooks](), [obsidian](), [open-source](), [productivity](), [pull-request]() ### AI overview This article argues that AI-assisted software development should prioritize design, planning, maintainability, and effective safeguards over raw lines of code. It presents habits involving Cursor Rules, Claude Code Skills, agent plugins, pull-request rules, reviews, hooks, and an Obsidian-based daily memory dump. ### Source excerpt Six habits that keep you fast and maintainable. Cursor Rules, Claude Code Skills, Agent Plugins, PR rules, non-nitpicky reviews, hooks, and Daily memory dump with Obsidian. ## Open-Source Network Simulators (2026 Edition) DevFeed: [Open-Source Network Simulators (2026 Edition)]() Original publisher: [Read original article]() Published: 2026-02-10T07:09:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Open Source](), [Vagrant]() Tags: [also](), [netlab](), [network](), [open-source](), [vagrant](), [worth-reading]() ### AI overview The article highlights Brian Linkletter's updated overview of open-source network simulators and emulators. It identifies containerlab and GNS3 as leading options, notes that the original vrnetlab is abandoned, and discusses using netlab primarily with containerlab while gradually phasing out Vagrant support. ### Source excerpt Brian Linkletter published an updated overview of open-source network simulators and emulators. containerlab and GNS3 are clear leaders (no surprise there) with the original vrnetlab becoming abandonware (fortunately, we have Roman Dodin's fork), which makes me think we should focus on using netlab primarily with containerlab and slowly sunset the Vagrant support, particularly considering some people actively hate the license change. Also, if anyone feels like writing an interface (provider module) between netlab and GNS3, the pull request would be most welcome 😎 Read more ... ## Pinning GitHub Actions DevFeed: [Pinning GitHub Actions]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2025-11-17T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [GitHub Actions](), [Security](), [supply chain attacks](), [CI/CD](), [Dependabot]() Tags: [also](), [ci-cd](), [commit](), [dependabot](), [github-actions](), [security](), [supply-chain-attacks](), [workflow]() ### AI overview This tutorial explains why GitHub Actions should be pinned to full commit SHAs instead of mutable tags or branches. It describes the security and auditability benefits and introduces caarlos0/pinata, a tool that automates pinning and creates pull requests for review. ### Source excerpt If you're using GitHub Actions in your projects, you should be pinning your actions to specific commit SHAs instead of using tags or branches. ## DevSecCon 2025 Recap: Securing the AI Revolution Together DevFeed: [DevSecCon 2025 Recap: Securing the AI Revolution Together]() Original publisher: [Read original article]() Author: Ben Desjardins Published: 2025-10-22T23:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Artificial Intelligence](), [DevSecOps](), [snyk](), [Application Security](), [Security](), [ide](), [Pull Request](), [snyk-code](), [Development]() Tags: [2025](), [ai](), [also](), [blog](), [developer](), [devops](), [devsecops](), [ide](), [interest](), [pmm](), [secure-software](), [security](), [snyk](), [snyk-code](), [snyk-open-source](), [snyk-platform]() ### AI overview This DevSecCon 2025 recap examines how AI is changing software development and security. It covers AI-accelerated DevSecOps, securing code from the first prompt, and managing AI-native application chaos with Evo by Snyk. The article also highlights Snyk capabilities for IDEs, pull requests, Snyk Code, and AppSec governance. ### Source excerpt AI is changing development. Our DevSecCon 2025 recap covers the 3 critical stages: AI-Accelerated DevSecOps, securing code at the first prompt, and taming AI-native app chaos with Evo by Snyk. ## Hacktoberfest 2025: How to Participate DevFeed: [Hacktoberfest 2025: How to Participate]() Original publisher: [Read original article]() Author: Haimantika Mitra Published: 2025-09-29T07:06:22Z Content type: tutorial Language: en Sources: [DigitalOcean]() Topics: [Hacktoberfest](), [Open Source](), [pull-requests](), [GitHub](), [GitLab](), [Maintainers]() Tags: [also](), [community](), [contribute](), [contributions](), [github](), [gitlab](), [hacktoberfest](), [maintainers](), [open-source]() ### AI overview A guide to participating in Hacktoberfest 2025, covering registration, contribution requirements, rewards, code contributions, and ways maintainers can prepare open-source projects. ### Source excerpt Hacktoberfest 2025: How to Participate Hacktoberfest registrations are live, and we're just a few days away from kicking off the month-long celebration of open source. Every October, developers from all over the world come together to contribute their skills, big and small, to open-source projects. Code is the most common way people participate, but that's not the only way you can help. Open source thrives on more than just commits. It needs documentation, testing, design, writing, and so much more. Before we get into the how, let's cover the basics. First, the rules of Hacktoberfest: Register anytime before October 31. Contribute to projects on GitHub or GitLab that have the hacktoberfest topic. Submit at least 6 high-quality pull/merge requests between October 1 and October 31. These need to be accepted by project maintainers to count. Rewards: Everyone who signs up and gets at least one PR merged, gets a digital badge from Holopin (you can get up to 4 badges). If you're among the first 10,000 people to complete 6 merged PRs/MRs, you'll also get a limited edition Hactoberfest 2025 t-shirt. That's it! You're ready to dive in. Ways to contribute: 1. Code Contributions This is what the majority of Hacktoberfest contributions consist of. Most participants jump in by submitting code to projects they care about. Maintainers, many of whom run projects purely out of passion, appreciate thoughtful, quality code more than anything. Whether this is your 12th Hacktoberfest or your very first pull request, now's the time to fire up GitHub or GitLab and get started. Helpful resources: Introduction to GitHub and Open-Source Projects How to use Git 5 things for your first time contributing 2. Maintaining a project Hacktoberfest isn't only for contributors. It's for maintainers too. If you've got a project idea that could help the community, you can launch it now and take part as a maintainer. If you're already maintaining an open-source project, here's how to prepare it for Hackt ## Sequoia Backs Zed's Vision for Collaborative Coding DevFeed: [Sequoia Backs Zed's Vision for Collaborative Coding]() Original publisher: [Read original article]() Author: Nathan Sobo Published: 2025-08-20T00:00:00Z Content type: news Language: en Sources: [Zed Industries - Blog]() Topics: [coding](), [ide](), [Development](), [Software](), [pull-requests](), [Git]() Tags: [ai-agents](), [also](), [code](), [collaboration](), [ide](), [software](), [version-control]() ### AI overview Zed announces a $32 million Series B led by Sequoia Capital, bringing its total funding to more than $42 million. The company plans to develop operation-based version control and integrate it into Zed to support collaboration among developers, teammates, and AI agents. ### Source excerpt This investment lets us pursue our vision for bringing a new kind of collaboration directly into the IDE. ## Learn How to Use Neon with AWS RDS to Boost Development Velocity in Postgres DevFeed: [Learn How to Use Neon with AWS RDS to Boost Development Velocity in Postgres]() Original publisher: [Read original article]() Author: Savannah Longoria Published: 2025-01-29T18:01:36Z Content type: tutorial Language: en Sources: [Blog -- Neon Docs]() Topics: [Amazon Web Services](), [Development](), [CI/CD](), [Testing](), [Database](), [Pull Request](), [API](), [Provisioning]() Tags: [also](), [api](), [aws](), [ci-cd](), [database](), [developer](), [development](), [how-to](), [infrastructure](), [pipelines](), [postgres](), [product](), [production](), [sandbox](), [scale](), [testing]() ### AI overview This tutorial explains how to use Neon as a Postgres development environment alongside AWS RDS for production. It covers database branching, ephemeral environments for pull requests and testing, CI/CD automation, isolated developer environments, and automatic scale-to-zero to reduce compute costs. ### Source excerpt AWS workshops are a fantastic free resource created by the AWS team to help you tackle real-world challenges using AWS infrastructure. As an AWS Partner, we'll be launching an AWS workshop to teach you how to use Neon as a development environment while keeping production workload... ## Adopting Docs as Code in Developer Workflows DevFeed: [Adopting Docs as Code in Developer Workflows]() Original publisher: [Read original article]() Author: Tiffany Chen Published: 2024-11-19T00:00:00Z Content type: tutorial Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [Git](), [Markdown](), [version-control](), [Pull Request]() Tags: [ai-trends](), [also](), [docs-as-code](), [documentation](), [git](), [markdown](), [version-control]() ### AI overview This article explains how a Docs as Code approach brings documentation into existing developer workflows through plain-text formats such as Markdown, Git-based version control, change reviews, and automated builds. It also recommends cultural practices such as recognizing documentation work in performance reviews and requiring documentation updates alongside code changes. ### Source excerpt We all suffer from documentation lagging behind product updates. ## Red in the real world DevFeed: [Red in the real world]() Original publisher: [Read original article]() Author: Unknown (noreply@blogger.com) Published: 2024-05-27T17:37:00Z Content type: article Language: en Sources: [Red]() Topics: [Red](), [XML](), [Parser](), [App](), [data-processing]() Tags: [also](), [code](), [data-processing](), [development](), [features](), [implementation](), [parsing](), [xml]() ### AI overview The article presents SmartXML, a commercial XML processor written in Red. Its author explains choosing Red to handle real-world XML data and avoid the complexity and breaking changes associated with many modern languages. ### Source excerpt We're often asked what Red can be used for, or what apps have been written in Red. Red can be used to write almost anything, but the sparse ecosystem and some missing pieces limit certain use cases. It's used a lot for in-house data processing, custom DSLs, simple GUI apps, and more. We also used it to build Redlake's DiaGrammar product. When we heard that someone had written a commercial app in Red, we thought that was great news, and we're here to tell you a little about it. Your first question is likely "What is it?" and the second "Where can I get it?". It's an XML processor, and you can find it here. The video on their site goes into detail about use cases and features, so we won't cover that here. We asked the author to talk about why they wrote SmartXML why those chose Red for the implementation. Here's what they had to say: Once I encountered the need to parse multiple XML files. I always thought that parsing tasks were very simple and that I wouldn't encounter any difficulties because there are things like XPath and XSD that, as I was told, solve all possible problems. However, I quickly realized that this was not the case, and some tools/standards only complicate life and are of little use for real-world usage. Thus, my XML parser project was born, which would allow working with real data rather than synthetic examples where XPath and XSD are truly effective. I chose Red because I was tired of the complexity of 90% of modern languages and the constant breaking changes in many of them. If you were to ask me what language I would choose to start a project with, looking back, I would still choose Red or perhaps try to use Hare (even considering that it's not yet completed) simply because I want to be sure that my solution will work in 10 or even 20 years. Initially, I thought I could finish within half a year, but the project took me many years. Nevertheless, I brought the project to completion. The main idea behind SmartXML was: 1. To make the parsing proces ## Keep your Chainguard Images up to date with digestabot DevFeed: [Keep your Chainguard Images up to date with digestabot]() Original publisher: [Read original article]() Published: 2023-12-18T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [chainguard](), [GitHub Actions](), [Pull Request](), [Security]() Tags: [also](), [chainguard](), [chainguard-images](), [container](), [continuous-integration](), [digestabot](), [dockerfiles](), [github-action](), [helm](), [make](), [merge](), [oidc](), [security](), [vulnerability-automation](), [vulnerability-management]() ### AI overview Chainguard's digestabot is a free GitHub Action that helps keep Chainguard Images and other container assets current. It detects outdated image digests, opens pull requests, and supports testing and secure updates through continuous integration and optional ephemeral OIDC tokens. ### Source excerpt Experience hassle-free updates with Chainguard's digestabot, ensuring your Images stay secure and up-to-date daily. ## A linter I really recommend you to use if you're doing SQL in Golang DevFeed: [A linter I really recommend you to use if you're doing SQL in Golang]() Original publisher: [Read original article]() Author: Piotr Jastrzebski Published: 2023-08-10T00:00:00Z Content type: tutorial Language: en Sources: [Turso Blog]() Topics: [SQL](), [Databases](), [ci](), [GitHub Actions](), [Deadlock](), [Command-line interface]() Tags: [also](), [ci](), [code](), [deadlock](), [github-actions](), [golang](), [sql](), [turso]() ### AI overview This final article in a series about resource leaks in SQL databases with Golang explains how to use the sqlclosecheck linter to detect database resources that are not closed. It demonstrates local usage and integration with GitHub Actions and golangci-lint so the check can run automatically. ### Source excerpt This is a final article of my mini series about the topic of leaking resources when using SQL databases in Golang. The whole series consists of three parts ## Scope functions DevFeed: [Scope functions]() Original publisher: [Read original article]() Published: 2022-09-23T00:05:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [functions](), [Library](), [object](), [Streams](), [Back end]() Tags: [also](), [apply](), [backend](), [functions](), [how-to](), [kotlin](), [let](), [scope-functions](), [standard-library](), [with](), [workshop-learning-programming]() ### AI overview A tutorial on Kotlin scope functions, including let, also, apply, and with. It explains how these standard-library extension functions transform or configure objects, presents application examples, and notes that scope-function-heavy code can make debugging harder. ### Source excerpt What is let, also, apply and with, and how to use them in our applications. ## Scopes and Scope Functions DevFeed: [Scopes and Scope Functions]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2022-08-22T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Kotlin](), [Library](), [Code]() Tags: [also](), [apply](), [classes](), [code](), [introduction](), [kotlin](), [learn](), [learn-to-program](), [let](), [library](), [programming](), [run](), [scope](), [scope-function](), [scope-functions](), [shadowing](), [standard](), [standard-library](), [variable](), [visibility](), [with]() ### AI overview A Kotlin tutorial chapter introduces scopes as regions of code where variables, functions, and classes can be declared, then begins explaining Kotlin's five scope functions from the standard library. ### Source excerpt In the last chapter, we learned how to create extension functions, which can be called using dot notation. In this chapter, we'll learn about scope functions, which are five particular functions that Kotlin gives us in its standard library. Before we can understand scope functions, though, it helps to first understand scopes. Introduction to Scopes In Kotlin, a scope is a section of code where we can declare new variables, functions, classes, and more. ## Nitpicky Code Reviews Are a Drag DevFeed: [Nitpicky Code Reviews Are a Drag]() Original publisher: [Read original article]() Author: Steve Barnegren Published: 2022-02-09T00:00:00Z Content type: opinion Language: en Sources: [Steve Barnegren]() Topics: [Code review](), [Pull Request](), [Code quality](), [engineering-culture]() Tags: [also](), [bug](), [code-quality](), [code-reviews](), [complexity](), [culture](), [reviews](), [team]() ### AI overview This opinion argues that code reviews should prioritize bugs, architectural improvements, and complexity reduction over harmless stylistic preferences. Excessive focus on conformity can create review noise without changing how the code works. ### Source excerpt Programmers can be a pedantic bunch. We like everything to be consistent. Uniform. Organised. Just so. ## Automating Code Analysis in Android Projects DevFeed: [Automating Code Analysis in Android Projects]() Original publisher: [Read original article]() Author: Kirill Rozov Published: 2021-09-20T18:11:42Z Content type: tutorial Language: en Sources: [Stories by Kirill Rozov on Medium]() Topics: [Android](), [Static code analysis](), [Code](), [Java](), [Kotlin](), [ci](), [ide]() Tags: [also](), [android](), [ci](), [code](), [code-analysis](), [code-quality](), [code-quality-tools](), [development](), [ide](), [java](), [kotlin]() ### AI overview This tutorial explains how to automate code analysis in Android projects. It distinguishes static analysis, which can run during development or in CI, from dynamic analysis, which runs the application to detect issues such as memory leaks. It also introduces IDE inspections as a code-analysis tool. ### Source excerpt Source unsplash.com/photos/Tjbk79TARiEAutomation of code analysis in Android projectsHello. My name is Kirill Rozov, and if you are interested in Android development, then most likely you have heard about the Android ResId Telegram channel with daily news for Android developers.https://medium.com/media/ff8acd16dd7b4b03a485bf9baab3c9d6/href Modern mobile applications are already quite serious enterprise projects that are developed by hundreds of developers, contain thousands of lines of code and are constantly changing and developing. The process of automating code checking and application work helps to deal with such a huge codebase. Today I will tell you what tools you can use to improve the stability of your project and avoid mistakes, as well as save time for colleagues during a pull request. Are you developing a project with a small team or alone? Then this article is even more important to you, since you most likely didn't configure any checks for yourself, and I will tell you why this needs to be done. Types of code checking Code analyzers is divided on two types: static code analysis (without starting the application) code analysis while the application is running Android development uses statically typed compiled languages: Java and Kotlin. These are important requirements for languages that allow them to analyze code without having to run it, and they can do it right at the time of writing the code. This type of analysis is called static. This makes it easy to run analyzing on any CI and automate checking for simple errors, such as not closing a stream after reading/writing code. The disadvantage of such checks is that if your code deviates from the template embedded in it, then the code will not work or will work incorrectly. Also, such analyzers can't understand complex code execution scenarios and their effect. More serious checks of your code can be done by automatically analyzing it while the application is running (dynamic). For example, you can tra ## Firebase Hosting adds preview channels, GitHub Actions integration, and version cloning DevFeed: [Firebase Hosting adds preview channels, GitHub Actions integration, and version cloning]() Original publisher: [Read original article]() Author: Ke Deng; Bryan Kendall Published: 2020-10-08T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [hosting](), [GitHub Actions](), [Firebase CLI](), [GitHub]() Tags: [also](), [firebase](), [firebase-cli](), [github](), [github-actions](), [hosting](), [launch](), [web]() ### AI overview Firebase announces preview channels for deploying development versions to temporary shareable URLs, along with an official GitHub Action and version cloning. Preview channels can be managed through the Firebase CLI or console and can be connected to pull request workflows. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Contributing To Open Source Projects The Right Way DevFeed: [Contributing To Open Source Projects The Right Way]() Original publisher: [Read original article]() Published: 2020-07-28T00:00:00Z Content type: tutorial Language: en Sources: [Markus Hatvan]() Topics: [Open Source](), [pull-requests](), [coding](), [Development]() Tags: [also](), [community](), [contribute](), [contributions](), [open-source]() ### AI overview A practical guide to contributing to open source projects, covering the skills and workflow knowledge needed to participate successfully. It discusses pull requests, commit messages, forking, upstream repositories, and ways to contribute through code, documentation, issue responses, and internationalization. ### Source excerpt When I started with open source contributions in April 2019, I remember being scared about doing everything wrong. ## EF-Supported Teams: Research & Development Update DevFeed: [EF-Supported Teams: Research & Development Update]() Original publisher: [Read original article]() Author: Ethereum Foundation Published: 2020-04-14T00:00:00Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [Blockchain](), [Development](), [releases](), [C++](), [Remote Procedure Call (RPC)](), [Testing](), [Zero-knowledge proof](), [Optimization](), [pass]() Tags: [also](), [c-plus-plus](), [community](), [development](), [ethereum](), [network](), [optimization](), [organizational](), [research-development](), [rpc](), [testing](), [zero-knowledge]() ### AI overview The Ethereum Foundation's update reports progress from EF-supported research and development teams. It highlights Aleth 1.8.0, including improvements to its RPC interface, blockchain synchronization, network protocol, testing tools, and consensus-related features, while noting that Aleth will receive only basic maintenance going forward. The article also discusses zero-knowledge proof application development on Ethereum. ### Source excerpt Friends, From our team to you and yours, we hope everyone and their families are well and keeping safe during these complicated weeks. To help pass some time while we're all stuck in doors, it's time again to update the community on progress made by some of the EF-supported... ## Automatic Merge of Pull Requests DevFeed: [Automatic Merge of Pull Requests]() Original publisher: [Read original article]() Published: 2020-03-01T07:01:57Z Content type: tutorial Language: en Sources: [Ariya Hidayat]() Topics: [Azure DevOps](), [Pull Request](), [CI/CD](), [GitHub](), [GitLab](), [bitbucket]() Tags: [also](), [azure](), [bitbucket](), [continuous-integration](), [devops](), [github](), [gitlab](), [pull-requests]() ### AI overview This tutorial explains Azure DevOps Auto Complete for pull requests. It describes configuring branch policies and build validation so approved pull requests are merged automatically after the continuous integration build succeeds, with options such as squashing, rebasing, fast-forwarding, and deleting the merged branch. ### Source excerpt After using Azure DevOps for a while, I am totally sold on its Auto Complete feature for pull requests. While it does not apply universally, I do believe that any development process should be at the level where merging pull requests, or generalizing it, integrating all forms of contribution, should be as automatic and as hassle-free as possible. ## July 2018 meeting minutes DevFeed: [July 2018 meeting minutes]() Original publisher: [Read original article]() Published: 2018-08-16T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Git](), [Submodules](), [btrfs](), [pull-requests]() Tags: [also](), [btrfs](), [free](), [git](), [open-source](), [os](), [react](), [reactos](), [reports](), [submodules](), [win32](), [winapi]() ### AI overview The ReactOS July 2018 meeting covered contributor status reports, the upcoming Hackfest, plans to split ReactOS components into Git submodules, and the project's 20th anniversary. Contributors also reported work on the 0.4.9 release, testing, web services, system information, WinBtrfs, and related bug fixes. ### Source excerpt 2018-08-02 19:00 UTC #meeting Proceedings Meeting started at 19:01 by Colin Finck. Point 1: Status Reports Point 2: Upcoming Hackfest Point 3: Splitting off ReactOS components into Git submodules Point 4: Celebrating 20 years of ReactOS Point 1: Status Reports Alexander Rechitskiy did some PR work for ReactOS and spread info about recent developments and the 0.4.9 release. Aleksandar Andrejevic mentioned he is thinking about continuing his audio work. [Next page]()