# Submodules Published articles for Submodules. 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 ## What's New for C++ Developers in Visual Studio 2026 (18.7 - 18.10) DevFeed: [What's New for C++ Developers in Visual Studio 2026 (18.7 - 18.10)]() Original publisher: [Read original article]() Author: Augustin Popa Published: 2026-09-14T06:38:16Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [Visual Studio 2026](), [C++](), [GitHub Copilot](), [MSVC](), [AI-assisted coding](), [CMake](), [Git](), [Submodules]() Tags: [2026](), [build-optimization](), [c-plus-plus](), [cmake](), [copilot](), [git](), [modernization](), [msvc](), [submodules](), [testing](), [tools](), [visual-studio](), [visual-studio-2026]() ### AI overview This Microsoft C++ Team Blog post recaps Visual Studio 2026 versions 18.7 through 18.10 for C++ developers. It covers C++ reliability fixes, GitHub Copilot modernization for upgrading MSBuild and CMake projects to newer MSVC Build Tools, improved code navigation, discoverable MSVC Build Tools installations, Git worktrees and submodules in the IDE, and debugging improvements. ### Source excerpt Over the past few months, we have continued shipping monthly Visual Studio 2026 releases, delivering improvements across all stages of the development cycle. In this blog post, we'll recap everything that changed from version 18.7 through 18.10 (released this month) that is relevant for C++ developers. This includes new tools for maintaining and navigating C++ [...] The post What's New for C++ Developers in Visual Studio 2026 (18.7 - 18.10) appeared first on C++ Team Blog. ## Gitte As Git Client For GNOME Continues Maturing Quite Nicely DevFeed: [Gitte As Git Client For GNOME Continues Maturing Quite Nicely]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-12T00:35:39Z Content type: news Language: en Sources: [Phoronix]() Topics: [Git](), [client](), [Submodules](), [Linux](), [App]() Tags: [app](), [bug-fixes](), [desktop](), [desktop-linux](), [git](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [release](), [submodules](), [ubuntu-benchmarks](), [ubuntu-hardware](), [ui]() ### AI overview Gitte 0.10 is a GTK4-based graphical Git client for GNOME and Linux. The release adds side-by-side diffs, Git LFS and submodule support, workflow shortcuts, UI improvements, and bug fixes. ### Source excerpt For those in pursuit of a graphical Git client for GNOME or the Linux desktop at large, the GTK4-powered Gitte continues advancing rather well and out this week is its v0.10 release... ## Today I will... manage Git Submodules without leaving the IDE DevFeed: [Today I will... manage Git Submodules without leaving the IDE]() Original publisher: [Read original article]() Author: Harshada Hole Published: 2026-08-11T17:05:31Z Content type: release Language: en Sources: [Visual Studio Blog]() Topics: [Visual Studio 2026](), [SDKs]() Tags: [command-line](), [feature](), [git](), [ide](), [submodules](), [update](), [visual-studio](), [visual-studio-2026]() ### AI overview Visual Studio 18.9 adds integrated Git submodule management. Developers can view, add, update, remove, and optionally activate submodules from the IDE, with submodules read-only by default. ### Source excerpt If you've worked with Git submodules for any length of time, you probably have a love-hate relationship with them. They're genuinely useful for pulling a shared library, an SDK, or common build scripts into your project. But actually working with them usually means tabbing over to a terminal and trying to remember whether it's git [...] The post Today I will... manage Git Submodules without leaving the IDE appeared first on Visual Studio Blog. ## What's new in Astro - August 2025 DevFeed: [What's new in Astro - August 2025]() Original publisher: [Read original article]() Author: Sarah Rainsberger Published: 2025-08-31T00:00:00Z Content type: news Language: en Sources: [The Astro Blog]() Topics: [Astro](), [VS Code Extension](), [Content Management System](), [Obsidian](), [Notion](), [GitHub](), [Submodules]() Tags: [2025](), [astro](), [github](), [news](), [submodules](), [updates](), [vscode]() ### AI overview This August 2025 Astro ecosystem update highlights Astro 5.13, including experimental environment-variable improvements and Chrome DevTools workspace support. It also covers Astro adoption, community projects, upcoming team appearances, and discussions about using Obsidian, Notion, or GitHub as content management systems for Astro sites. ### Source excerpt August 2025 - 1 million Astro VSCode extension installs, easier ways to contribute to Astro, and more! ## Assorted Git things DevFeed: [Assorted Git things]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2024-10-01T08:27:00Z Content type: article Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Git](), [Submodules](), [ide](), [passwords]() Tags: [concepts](), [git](), [ide](), [password](), [submodules](), [til]() ### AI overview A running collection of Git tips covering editor configuration, staging behavior, removing submodules, credential-helper interaction, and maintaining a fork. ### Source excerpt A running log of Git concepts I've learned since I started journaling ## Create a Virtual Bookshelf with Hugo and PaperMod DevFeed: [Create a Virtual Bookshelf with Hugo and PaperMod]() Original publisher: [Read original article]() Author: Tom Published: 2024-04-26T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Hugo](), [API](), [Git](), [YAML]() Tags: [book-organization](), [git](), [how-to](), [hugo](), [hugo-bookshelf](), [hugo-site-customization](), [installation](), [papermod](), [papermod-theme](), [reading-list-sharing](), [submodules](), [virtual-bookshelf](), [yaml]() ### AI overview A tutorial for creating a virtual bookshelf on a Hugo site with the PaperMod theme. It explains the motivation for organizing books as blog posts and provides installation and usage guidance for the bookshelf theme, including Git submodules and book metadata. ### Source excerpt Learn how to create a virtual bookshelf on your Hugo site using the PaperMod theme, allowing you to organize and share your reading list with ease. ## How Apollo Manages Swift Packages in a Monorepo with Git Subtrees DevFeed: [How Apollo Manages Swift Packages in a Monorepo with Git Subtrees]() Original publisher: [Read original article]() Author: Zach FettersMoore Published: 2024-01-30T07:45:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [monorepo](), [Swift](), [swift-package-manager](), [Git](), [Submodules](), [Library](), [Package manager](), [iOS](), [Code](), [Development]() Tags: [development](), [git](), [ios](), [library](), [mobile](), [monorepo](), [packages](), [pull-requests](), [submodules](), [swift](), [swift-package](), [swift-package-manager](), [testing]() ### AI overview The article describes Apollo iOS's challenges with managing multiple Swift Package Manager library targets in a monorepo. It explains the goal of distributing smaller, independently versioned packages while preserving an efficient shared development and testing workflow, and discusses Git submodules as one approach and its operational drawbacks. ### Source excerpt The monorepo is a common structure for many software projects, and Apollo iOS is no different. Our project was structured in a single repo containing many different Swift Package Manager (SPM) library targets, along with test code and code only used as part of development. This presents a few problems however, one being that when a user adds the SPM package as a dependency, it will pull down all of the code and files in the repo, even though most of them aren't needed. ## Magic enter command for (fish/zsh) shell DevFeed: [Magic enter command for (fish/zsh) shell]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2022-07-23T19:50:31Z Content type: tutorial Language: en Sources: [Kaushik Gopal's Site]() Topics: [friendly interactive shell](), [Zsh](), [Shell](), [Git](), [Command-line interface]() Tags: [command-line](), [commands](), [git](), [issue](), [submodules]() ### AI overview A tutorial for fish and zsh users that binds the Enter key to run git-number in Git repositories with changes, or ls -lh elsewhere when the command line is empty. ### Source excerpt Two of the most common commands I run when I cd into a directory are: git status (which i do through git-number) ls -lh (aliased automatically as ll through fish) If this directory is not a git repo, then I usually am thinking of command 2. If however it is a git repository then I'd like to know if any files have been changed in this directory and which ones specifically (which is command 1). Wouldn't it be nice if I could just hit the ↩ (enter key) and have this automatically happen? Your browser doesn't support HTML5 video. Download the video instead. Solution for fish users ## If you're using fish, I got you covered: # filename: fish/conf.d/magic-enter.fish function magic-enter-cmd --description "Issue git status or ls on hitting enter in a dir" set -l cmd ll set -l is_git_repository (fish -c "git rev-parse --is-inside-work-tree >&2" 2>| grep true) # Special variable indicating git. set -l in_root_folder (fish -c "git rev-parse --show-toplevel >&2" 2>| grep (pwd)) set -l repo_has_changes (git status -s --ignore-submodules=dirty) if test -n "$is_git_repository" if test -n "$in_root_folder" if test -n "$repo_has_changes" set cmd git-number end end end echo $cmd end function magic-enter set -l cmd (commandline) if test -z "$cmd" commandline -r (magic-enter-cmd) commandline -f suppress-autosuggestion end commandline -f execute end bind \r magic-enter Solution for zsh users ## If you're using zsh, I adapted the native solution like so: # filename: magic-enter.plugin.zsh # Default commands : ${MAGIC_ENTER_GIT_COMMAND:="git-number"} # run when in a git repository : ${MAGIC_ENTER_OTHER_COMMAND:="ll"} # run anywhere else magic-enter() { # Only run MAGIC_ENTER commands when in PS1 and command line is empty # http://zsh.sourceforge.net/Doc/Release/Zsh-Line-Editor.html#User_002dDefined-Widgets if [[ -n "$BUFFER" || "$CONTEXT" != start ]]; then return fi is_git_repository=$(git rev-parse --is-inside-work-tree) in_repo_root_folder=$(git rev-parse --show-toplevel) repo_has_chan ## Supabase Studio DevFeed: [Supabase Studio]() Original publisher: [Read original article]() Author: Paul Copplestone Published: 2021-11-30T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Open Source](), [hosting](), [Front end](), [Git](), [Submodules]() Tags: [development](), [feature-flags](), [frontend](), [git](), [hosting](), [open-source](), [self-hosting](), [submodules]() ### AI overview Supabase announces Supabase Studio, making the Dashboard used on its Platform available for local development and self-hosting. The article explains the challenges of maintaining separate codebases and describes the decision to open source a shared frontend codebase for the Platform and Self-Hosting, including approaches involving Git submodules, synchronization tools, APIs, and feature flags. ### Source excerpt The same Dashboard that you're using on our Platform is now available for local development and Self-Hosting. ## Kdoc for Android libraries using Dokka DevFeed: [Kdoc for Android libraries using Dokka]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2020-02-19T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Documentation](), [generate documentation](), [Kotlin](), [Library](), [modules](), [Gradle](), [Submodules](), [GitHub Pages]() Tags: [blogs](), [documentation](), [dokka](), [generate-documentation](), [github-pages](), [gradle](), [kdoc](), [kotlin](), [library](), [module](), [submodules]() ### AI overview This tutorial explains how to generate KDoc for Kotlin libraries with the Dokka Gradle plugin. It covers basic configuration, output formats, and challenges involving multi-module libraries, submodule sources, and API visibility. ### Source excerpt A great way to make your library easier to use it to generate code documentation for its public interface. The default way to do this in Kotlin is to generate KDoc using the official Dokka plugin. ## 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. ## Introducing git fastclone DevFeed: [Introducing git fastclone]() Original publisher: [Read original article]() Author: Square Engineering Published: 2015-11-16T17:10:00Z Content type: tutorial Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Git](), [Submodules](), [Caching](), [build times](), [Concurrency]() Tags: [build](), [build-times](), [caching](), [engineering](), [git](), [go](), [how-to](), [incremental](), [submodules](), [thread]() ### AI overview This article introduces git fastclone, a Ruby gem that speeds up repeated Git clones involving repositories and submodules. It uses reference repositories, mirrors, caching, prefetching, and multithreaded updates to support faster checkouts for CI and development. ### Source excerpt How to make your clones go by much faster. ## Parson: A Simple, Compact C Library for Processing JSON DevFeed: [Parson: A Simple, Compact C Library for Processing JSON]() Original publisher: [Read original article]() Published: 2014-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [C](), [JSON](), [Library](), [API](), [Git](), [Submodules](), [GitHub]() Tags: [api](), [c](), [git](), [github](), [how-to](), [json](), [library](), [submodules]() ### AI overview This tutorial introduces Parson, a compact C library for processing JSON. It explains the library's small interface, methods for traversing nested objects and arrays, integration using two files, and an example that parses commit data from GitHub's API. ### Source excerpt A simple and compact C library for JSON processing ## Kochiku Improvements for Test Sharding at Square DevFeed: [Kochiku Improvements for Test Sharding at Square]() Original publisher: [Read original article]() Author: Square Engineering Published: 2014-08-08T16:07:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Open Source](), [Caching](), [dashboards](), [Amazon EC2](), [GitHub](), [Submodules](), [configuration](), [Refactoring](), [Maven]() Tags: [amazon-ec2](), [caching](), [configuration](), [ec2](), [engineering](), [github](), [new-features](), [open-source](), [sharding](), [submodules]() ### AI overview Square describes improvements to Kochiku, its open-source tool for partitioning test suites across workers running in Amazon EC2. The updates include worker health tracking, action caching, cluster auto-scaling, improved submodule support, richer build emails, repository-based configuration, project health tracking, and a new Maven partitioner. ### Source excerpt Kochiku is getting plenty of attention from the new CII team. ## Objective-C on Travis-CI DevFeed: [Objective-C on Travis-CI]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2013-04-11T22:58:00Z Content type: tutorial Language: en Sources: [Keith Smiley]() Topics: [Objective-C](), [Continuous integration](), [iOS](), [Xcode](), [Testing](), [GitHub](), [Jenkins](), [Open Source]() Tags: [apple](), [ci](), [configuration](), [continuous-integration](), [dependencies](), [github](), [ios](), [jenkins](), [objective-c](), [open-source](), [self-hosted](), [submodules](), [testing](), [travis](), [travis-ci](), [xcode]() ### AI overview A practical guide to configuring Travis CI for Objective-C projects targeting OS X and iOS. It covers repository setup, the .travis.yml configuration file, Xcode shared schemes and test targets, dependency handling, and additional scripts for projects using CocoaPods or submodules. ### Source excerpt Recently Travis added support for Objective-C and there for OS X and iOS projects for continuous integration testing. I gather that people have previously done this with self-hosted dedicated Jenkins machines but since Apple is so aggressive about dropping support for previous versions of the OS it seems like a pain to have to replace your build server every few years. Enter Travis, a great hosted continuous integration server that hosts a huge amount of open source projects. I figured with this new support I could host some of my smaller libraries just to set how well it worked. The initial setup process was a bit tedious but I eventually got it to work. Assumtions: You have a test framework already integrated with your project (I like Specta/Expecta) You have your project on Github in a public repository. Travis offers a pro account if you'd rather Steps Create a .travis.yml file in the root of your repository (leading dot is intentional). For many projects a file may just look like: language: objective-c By default Travis runs this script for Objective-C projects I was informed on Twitter that the current script that runs Objective-C projects is actually located here. It was originally created by Justin Spahr-Summers here. This script seems to run my projects without any issue, they just occasionally require more initial setup (we'll get to that). Enable your repository in Travis' settings. From your Travis profile page (after signing in with Github) you should see a list of your repositories, you may have to press 'Sync now', where you can switch on the repository you're planning on adding. Configure your project within Xcode. As I assumed above you already have a test target setup. You do have to do a few things in Xcode to make everything work correctly. Go to 'Manage Schemes' in Xcode. Check the 'Shared' box for the scheme that needs to be run. Click 'Edit...' in the bottom left and go to your build action. On the row of your Tests target check the box in the ' ## Some useful git aliases DevFeed: [Some useful git aliases]() Original publisher: [Read original article]() Published: 2011-05-13T00:00:00Z Content type: tutorial Language: en Sources: [Tim Kellogg]() Topics: [Git](), [Submodules]() Tags: [config](), [git](), [git-aliases](), [global](), [graph](), [submodules](), [useful]() ### AI overview A collection of Git aliases for displaying formatted repository history, pulling updates for a repository and its submodules, and resetting repositories to a clean state by removing changes and untracked or ignored files. ### Source excerpt Git aliases are a great way to do more with less typing. Our team uses submodules to an extent which can sometimes be confusing. Some of these aliases help to clarify behavior. These are a few of my favorites.git lgThis gives you a nicely formatted semi-graphical log view with users, branches, and remotesgit config --global alias.lg "log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %C(green)%an%Creset %Cgreen(%cr)%Creset' --abbrev-commit --date=relative" git latestThis does a git pull on the current repository as well as all submodulesgit config --global alias.latest '!sh -c "git pull && git submodule foreach \"git pull\""'git virgin (getting to a pure state)This will reset your changes and delete all untracked and ignored files (includes bin/ and obj/ directories)git config --global alias.virgin '!sh -c "git reset HEAD --hard && git clean -fXd && git clean -fd"'git harem (a whole lot of virgins)This does a virgin for your repository as well as all submodulesgit config --global alias.harem '!sh -c "git virgin && git submodule \"git harem\""' ## A preference for distributed version control and Git workflows DevFeed: [A preference for distributed version control and Git workflows]() Original publisher: [Read original article]() Published: 2011-03-03T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [version-control](), [Git](), [Pull Request](), [Open Source](), [Framework](), [Submodules]() Tags: [git](), [open-source](), [patches](), [pull-request](), [submodules](), [version-control]() ### AI overview The author explains a preference for distributed version control over SVN or TFS, emphasizing pull requests for contributing patches and Git features such as git-svn and submodules. ### Source excerpt Today i was looking at open source workflow frameworks for work today and paused on objectflow. I almost decided not to use the library because they're still using SVN or TFS (I'm not real sure which) even though codeplex supports Mecurial.I'm coming in with the idea that I may contribute to the project if I find, down the road, that I have something that could be added to the project. Submitting patches seems so painful compared to a simple pull request. The workflow of a distributed version control system (DVCS) makes sharing code so incredibly easy that it causes me psychological pain to think about going back to SVN.On the other hand, one benefit of objectflow being available as SVN is that I can easily use git-svn to create a git clone that can be included as a submodule. It wouldn't be quite as straight-forward if it were a mecurial repository. Submodules are an excellent feature of Git!