# repo A repo, or repository, is a place in a version control system that hosts application source code and metadata. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Inside the AI Stack of an $8.3B AI Company's Product Team | Together AI DevFeed: [Inside the AI Stack of an $8.3B AI Company's Product Team | Together AI]() Original publisher: [Read original article]() Author: Aakash Gupta Published: 2026-09-14T23:05:28Z Content type: article Language: en Sources: [Product Growth]() Topics: [Artificial Intelligence](), [context](), [repo](), [context window](), [Developer experience](), [GitHub](), [Linear]() Tags: [ai](), [context](), [context-window](), [developer-experience](), [github](), [linear](), [product](), [repo](), [team](), [tools]() ### AI overview The article examines Together AI's AI-oriented product team and describes four parts of its working stack: a shared context repository, reusable skills for research and product documentation, an orchestrator for product leaders, and agent evaluations. It explains how shared context files and workflows support collaboration across product areas, including automated weekly status updates using Linear, GitHub, and strategy documents. ### Source excerpt I got a truly AI-pilled product team to demo the 4 key tools in their stack ## commit-rewriter 0.1 DevFeed: [commit-rewriter 0.1]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-09-14T00:28:10Z Content type: release Language: en Sources: [Simon Willison's Weblog]() Topics: [releases](), [repo](), [coding](), [Git](), [Python]() Tags: [ai-assisted-programming](), [ai-assisted-programming-407](), [git](), [git-55](), [projects](), [projects-553](), [python](), [python-1-283]() ### AI overview Release announcement for commit-rewriter 0.1, a small web app that edits repository commit messages and rewrites commits from the first edited commit through the latest one. It creates a timestamped branch of the current repository state so changes can be reverted. ### Source excerpt Release: commit-rewriter 0.1 I built this little web app the other day to help edit the commit messages for the Datasette security releases. The initial commits were full of coding agent cruft and references to issue IDs from our private repository, so they weren't fit for publication. If you want to edit the commit messages for a repository you can run it like this: uvx commit-rewriter path/to/repo Omit the path if you are already in the directory for that repo. When you submit your edits the tool creates a timestamped branch of your current repo state - to allow you to revert if you need to - and then rewrites every commit from the first one you edited to the most recent. Tags: git, projects, python, ai-assisted-programming ## How Srini Raghavan helped $3.4B SaaS Giant Freshworks Embrace the AI PDLC DevFeed: [How Srini Raghavan helped $3.4B SaaS Giant Freshworks Embrace the AI PDLC]() Original publisher: [Read original article]() Author: Aakash Gupta Published: 2026-08-24T23:16:09Z Content type: article Language: en Sources: [Product Growth]() Topics: [Software as a service](), [AI Agent](), [cursor](), [Design system](), [context](), [repo]() Tags: [ai](), [ai-agent](), [context](), [cursor](), [design-system](), [repo](), [saas]() ### AI overview The article summarizes how Freshworks moved from a six-month release process to a two-week cycle under Chief Product Officer Srini Raghavan. It describes an AI product development lifecycle built on structured data, a parsable design system, documented coding standards, a single source repository, contextual knowledge hubs, reusable AI builder artifacts, governed AI agents, and an evaluation phase. ### Source excerpt + Why he uses Grok models, and the future of the "Product Builder" role ## Migrating a Large Flow Monorepo to TypeScript DevFeed: [Migrating a Large Flow Monorepo to TypeScript]() Original publisher: [Read original article]() Author: Shawn Walton, Software Engineer Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Yelp]() Topics: [monorepo](), [TypeScript](), [migration](), [repo](), [Code]() Tags: [coverage](), [integrity](), [migration](), [monorepo](), [open-source](), [rewrite](), [typescript]() ### AI overview Yelp describes its gradual migration of a large Flow monorepo to TypeScript. The team chose a package-by-package approach to preserve type-checking trust and type safety while Flow and TypeScript coexisted in production, using open-source conversion tooling, custom codemods, and manual fixes. ### Source excerpt In early 2017, Webcore selected Flow as Yelp's next-generation typechecker over TypeScript. At the time there was no clear frontrunner. Flow had better support for React, better performance, and a respectable repository of types for NPM packages in flow-typed. However, a few years later the landscape had shifted, and it became clear that TypeScript was emerging as the stronger choice. TypeScript's DefinitelyTyped repo had thousands more packages than flow-typed, and many more packages shipped with built-in TypeScript headers. TypeScript also proved to be more stable over time, and limited uptake in the wider JS community made finding tools and documentation... ## Forking an open source project DevFeed: [Forking an open source project]() Original publisher: [Read original article]() Author: jonskeet Published: 2026-07-11T12:54:14Z Content type: opinion Language: en Sources: [Jon Skeet]() Topics: [MIDI](), [Open Source](), [Windows 11](), [NuGet](), [repo](), [.NET]() Tags: [c-sharp](), [nuget](), [open-source](), [release](), [repo](), [windows-11]() ### AI overview The author explains why managed-midi stopped working properly on fully updated Windows 11 installations and discusses plans to potentially publish and maintain a fork after fixes were accepted by the original author. ### Source excerpt Introduction and motivation Some of the projects I work on - notably V-Drum Explorer and At Your Service - use MIDI to interact with hardware devices. I use a couple of packages for this depending on the nature of the interaction, but the one I use most often is managed-midi, which currently has its "source ... Continue reading Forking an open source project -> ## Introducing Kempt DevFeed: [Introducing Kempt]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2026-06-23T00:00:23Z Content type: release Language: en Sources: [Zac Sweers]() Topics: [formatting](), [pre-commit](), [hooks](), [ci](), [repo](), [Java](), [Kotlin](), [Rust]() Tags: [ci](), [formatting](), [gradle](), [hooks](), [java](), [kotlin](), [open-source](), [pre-commit](), [repo](), [rust]() ### AI overview The article introduces Kempt, a small project designed to replace heavy Gradle-based formatting setups with a repo-local pipeline for formatting and commit hooks. It supports Kotlin, Java, and Rust, and can run locally, in pre-commit hooks, and in CI. ### Source excerpt Formatting should be boring, in the best possible way. ## What Did the Agent Just Push? Auditing Git for AI Agents DevFeed: [What Did the Agent Just Push? Auditing Git for AI Agents]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-06-20T00:00:00Z Content type: tutorial Language: en Sources: [Eugene Petrenko]() Topics: [Git](), [AI Agent](), [audit](), [Clash](), [hooks](), [repo]() Tags: [ai-agents](), [ai-coding](), [audit](), [eugene-petrenko](), [git](), [hooks](), [infrastructure](), [jonnyzzz](), [proxy](), [pull-request](), [repo](), [tag-41199d53f463](), [workflow]() ### AI overview This article presents an approach for auditing autonomous AI agents that work with Git repositories. It recommends keeping real credentials away from agents, using a Git proxy as a hard boundary to limit which branches can change, and using Git hooks as a lighter, best-effort layer for provenance and telemetry. ### Source excerpt When you hand a repo to an autonomous AI Agent, you need to bound what it can touch and capture what it did. Part 1 -- the approach -- keep the keys away from the agent, a git proxy as the hard boundary, and git hooks as the lighter alternative. ## From Figma to code in minutes: How I built UI Studio with AI DevFeed: [From Figma to code in minutes: How I built UI Studio with AI]() Original publisher: [Read original article]() Author: Jayant Kumar Published: 2026-06-18T07:01:03Z Content type: tutorial Language: en Sources: [Amex GBT Technology]() Topics: [Figma](), [ui](), [React](), [Anthropic Claude](), [Prompt Engineering](), [repo](), [Terminal]() Tags: [ai](), [anthropic-claude](), [figma](), [frontend-development](), [prompt-engineering](), [react](), [repo](), [software-development](), [terminal](), [ui](), [ui-design]() ### AI overview This tutorial explains how the author built UI Studio, a tool that generates UI code using Egencia's internal UITK React components from a prompt, a Figma URL, or a screenshot. It describes the original feasibility-checking workflow and the tool's progression from a local prototype to a deployable application. ### Source excerpt Whether you're a developer checking feasibility or a designer wanting to see your Figma come to life in real code, UI Studio is built for both. If you've ever worked on a product team, you know the dance, a designer hands over a Figma file, but before anyone writes a single line of production code, a developer has to answer one question: Is this buildable with our component library? At Egencia by Amex GBT, we use UITK (UI Toolkit), our internal component library built on React. It gives developers a set of standardized components to build consistent UIs across our products. As part of Egencia, that question kicks off a process that can take days. We open the doc site, scan the components, write some test code in the React playground or our own repo, and eventually come back to the designer with a verdict. If something isn't feasible, the design goes back for revisions. Then we check again and finally start building. It works. But it's slow. And I couldn't help but wonder whether there was a better way. The idea Earlier this year, I was doing the Anthropic Claude course and somewhere between learning about prompt engineering and working through the hands-on labs, it clicked. What if I could skip the whole feasibility loop and just generate the UI directly using our actual UITK components, from a prompt, a Figma link, or even a screenshot? That was the seed. A few weeks later, UI Studio was live. Figure 1: UI Studio, describe what you want, drop an image, or paste a Figma URLHow it got built It took about three to four weeks to build, and it wasn't linear. It went through three very different versions before becoming what it is today. Phase 1: The hacky local version The first version was built to prove the idea, not to share it. I cloned the UITK doc site repo locally, fetched component data directly from it, and created a proxy that passed all user input to the model via terminal. It worked on my machine. But getting anyone else to use it would have meant cloning re ## Using Git Worktrees to Run Multiple Claude Code Sessions in Parallel DevFeed: [Using Git Worktrees to Run Multiple Claude Code Sessions in Parallel]() Original publisher: [Read original article]() Author: Eric Roby Published: 2026-05-12T14:08:41Z Content type: tutorial Language: en Sources: [Eric Roby]() Topics: [Git](), [Claude Code](), [Command-line interface](), [repo]() Tags: [agents](), [claude-code](), [context](), [git](), [parallel](), [repo](), [workflow]() ### AI overview The article explains how Git worktrees let developers run multiple Claude Code sessions simultaneously in isolated working directories. It argues that this avoids shared-checkout conflicts and reduces context switching while preserving shared repository history and objects. ### Source excerpt Stop running one Claude Code session at a time. ## OLX Masterclass Frontend 2026 DevFeed: [OLX Masterclass Frontend 2026]() Original publisher: [Read original article]() Author: Isaac Queiroz Published: 2026-02-25T16:16:00Z Content type: news Language: en Sources: [OLX]() Topics: [Front end](), [Model Context Protocol](), [Development](), [CSS](), [React](), [Figma](), [repo](), [configuration]() Tags: [2026](), [agents](), [ai](), [code](), [coding](), [component](), [configuration](), [css](), [development](), [event](), [figma](), [frontend](), [frontend-development](), [masterclass](), [mcp](), [mcps](), [model-context-protocol](), [olx](), [react](), [repo]() ### AI overview OLX announces its 2026 Frontend Masterclass, featuring three sessions on MCP integrations and Figma-to-React workflows, new CSS capabilities, and managing localized websites for multiple brands from a single repository. ### Source excerpt The always-evolving challenges of OLX create a rich environment for innovation, experimentation, and knowledge sharing. In our 2026 Frontend Masterclass, we have three sessions that will shed light on our current development flow. Join us on March 3rd, 2026, from 6:00 pm to 9:00 pm at our OLX Offices in Poznań! Do you want to join us and know what's trending in the latest frontend technology? Check the event information and join here! Can't join it in person? Sign in to this form to receive the online recording of the session! Our Agenda With a broad schedule, our speakers will deliver a mix of technical presentations and demonstrations on multiple subjects. MCP Servers in Action: From Figma Design to React Component in Minutes by Karol Grabowski Part of what changed in our day-to-day flow is how AI is always available to help us. AI assistants and agents are powerful out-of-the-box tools; we can augment our reach by configuring Model Context Protocols (MCPs) to take our setup a step further. Join Karol to explore how the Model Context Protocol turns AI assistants into powerful development partners with direct access to your tools. This talk covers the MCP ecosystem, real OLX integrations, and includes a live coding session demonstrating the Figma-to-code workflow. CSS is no longer "this simple" -- it got _layers_, quite literally by Tomasz "Comandeer" Jakut At the same time that we advance with AI and multiple experiments to learn from our users and make our flows as pleasant as possible, we are still styling our components with the usual suspects, right? Not always! Join Tomasz Jakut and deep dive into CSS's new capabilities that can redefine how we approach styling websites: from @Layer and nesting to container queries, scoped styles, and user preferences. New native features can refresh well-known techniques and make others obsolete. One-product, three brands -- Our strategy for serving different countries from a single repo by Lilian Galezewska We all know how OL ## How to Split a Git Mono-Repository While Preserving File History DevFeed: [How to Split a Git Mono-Repository While Preserving File History]() Original publisher: [Read original article]() Author: Tom Published: 2025-09-02T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Git](), [repo](), [Script](), [Python]() Tags: [automation](), [bash](), [best-practices](), [devops](), [git](), [git-filter-repo](), [history](), [history-preservation](), [how-to](), [migration](), [mono-repo](), [open-source](), [repository](), [repository-split](), [run](), [software-engineering](), [tutorial](), [verify](), [version-control](), [workflow]() ### AI overview A tutorial for splitting a large Git mono-repository into smaller repositories while preserving the history of selected files. It covers cloning the repository, disconnecting the old remote, filtering history, cleaning up unreferenced data, configuring a new origin, and pushing and verifying the result. ### Source excerpt This guide explains how to split a mono-repo into smaller repositories, keeping the git history for selected files. ## Using Compose Hot Reload to Build a Vaporwave-Inspired Compose Desktop Project DevFeed: [Using Compose Hot Reload to Build a Vaporwave-Inspired Compose Desktop Project]() Original publisher: [Read original article]() Published: 2025-06-09T10:52:55Z Content type: tutorial Language: en Sources: [maiatoday]() Topics: [compose-hot-reload](), [Compose](), [Kotlin](), [Gradle](), [multiplatform](), [repo]() Tags: [animate](), [code](), [compose](), [compose-hot-reload](), [gradle](), [kotlin](), [multiplatform](), [reload](), [repo](), [vaporwave]() ### AI overview An exploratory tutorial on using JetBrains Compose Hot Reload in a Compose Desktop project, with Vaporwave as the visual theme. It covers project setup, Kotlin 2.1.20 or later, plugin configuration, the foojay resolver, and running the application. ### Source excerpt Why I want to play with the recently released Compose Hot reload feature by JetBrains. To do this I setup a Desktop compose project and picked a topic to draw and explore: Vaporwave Why? because Vaporwave is a curious Internet thing. It has a strong visual aesthetic that I wanted to recreate. It is intriguing. It is seems to be a fleeting transient phenomena: it is in the name vapor and wave and yet... and yet we see it pop up in unexpected places. It is a form of hauntology: a cultural idea that returns from the past to haunt the present. There will be ramblings interspersed and remixed with code, I will put the code at the beginning of the sections, so that you can easily skim if remix-rambling is not your thing. Yes, there is a matching repo. Yes, it is a mix of organic hand coding and AI enhancements. I will explain my process. But first Setting up Hot Reload You need: A project that has a Compose desktop part. It can be stand alone or part of a multiplatform project Use a Kotlin version 2.1.20 or later Get the plugin and the latest version information and add it the place you keep your versions, like a toml file Setup the plugin in your build.gradle.kts Setup the foojay resolver Run the main application from the gutter icon or command line. something like ./gradlew runHot --mainClass MainKt --auto Optional extra make a run target for your particular main application if you have more than one See and example of each line in the sample repo Wow these instructions are vague! indeed things change quickly. Please follow the original repo. This post will date. Origins and Sound track Vaporwave appeared as a music genre with a strong aesthetic, some say in 2010. The iconic album Floral Shoppe by Macintosh Plus is still available and makes a perfect sound track for inspecting the code or reading this article. Go ahead click the link and start the music. I'll wait. We are on the cusp of widespread changes in how we interact with technology. Will we have nostalgia for the ## Ekapkgs, a poly-repo fork of Nixpkgs DevFeed: [Ekapkgs, a poly-repo fork of Nixpkgs]() Original publisher: [Read original article]() Author: Jon Ringer Published: 2025-03-31T00:00:00Z Content type: opinion Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [repo](), [Development](), [Maintainability](), [cloud-infrastructure]() Tags: [development](), [fork](), [glibc](), [infrastructure](), [maintainability](), [openssl](), [repo]() ### AI overview The article presents Ekapkgs as a poly-repository fork of Nixpkgs. It argues that Nixpkgs' monolithic scale, lengthy RFC process, and staging workflow make maintenance, convention changes, and package updates difficult, while separate repositories could enable faster iteration and more focused curation. ### Source excerpt Ekapkgs forks Nixpkgs, splitting it into repos for faster updates & easier curation. Ditch monolithic development flows & slow RFCs. Innovate freely! ## GitPortal: Bidirectional, Eventual Code Sharing for KMP Teams DevFeed: [GitPortal: Bidirectional, Eventual Code Sharing for KMP Teams]() Original publisher: [Read original article]() Published: 2024-06-26T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [multiplatform](), [Mobile](), [Code](), [repo]() Tags: [adopting](), [architecture](), [code-sharing](), [git](), [kmp](), [mobile](), [repo]() ### AI overview This introductory article explains why the default single-repository KMP setup can be difficult for native mobile teams whose Android and iOS specialists work independently. It introduces GitPortal's bidirectional mode as an approach for sharing KMP logic while keeping native app development workflows separate. ### Source excerpt For teams scaling KMP, versioned libraries are inefficient. Merging app code and KMP code into a single repo may be impractical, and introduces its own issues. GitPortal allows bidirectional, eventual code sharing. ## Part 1: Repo and CI Setup - Kevin Galligan DevFeed: [Part 1: Repo and CI Setup - Kevin Galligan]() Original publisher: [Read original article]() Published: 2024-05-19T00:00:00Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Tutorial](), [repo](), [ci](), [GitHub](), [GitHub CLI extension](), [Kotlin](), [Android](), [iOS]() Tags: [ci](), [cli](), [github](), [how-to](), [install](), [kotlin](), [repo](), [setup]() ### AI overview Part 1 of a tutorial series that creates a Kotlin Multiplatform repository and separate Android and iOS app repositories, links them with GitPortal, and configures CI to communicate between them. ### Source excerpt For teams piloting KMP, direct access to the Kotlin source is the best way to get started. Use GitPortal to link and sync KMP source from an external repo. In Part 1, we'll install GitPortal, set up the three source code repos, and configure CI to monitor everything. ## How to interview DevOps candidates? DevFeed: [How to interview DevOps candidates?]() Original publisher: [Read original article]() Author: Tom Published: 2024-01-23T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [DevOps](), [repo](), [Terraform](), [Python]() Tags: [devops](), [devops-hiring-tips](), [devops-interview-questions](), [evaluating-devops-skills](), [hiring](), [how-to](), [interview](), [interviewing-devops-candidates](), [practical-devops-assessments](), [technical-interview-strategies]() ### AI overview The article argues that DevOps interviews should use practical, job-relevant assessments instead of artificial tests based on constrained environments or encyclopedic recall. It recommends sharing an imperfect repository in advance and discussing suggested improvements across infrastructure, code, secrets, and project hygiene. ### Source excerpt Learn effective strategies for interviewing DevOps candidates, including practical exercises and review-based assessments to evaluate their skills and fit. ## Stampeding Elephants DevFeed: [Stampeding Elephants]() Original publisher: [Read original article]() Author: Tony Robalik Published: 2023-01-31T06:00:00Z Content type: opinion Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Software Engineering](), [Gradle](), [modules](), [repo](), [Caching](), [ci]() Tags: [best-practices](), [caching](), [ci](), [engineering](), [gradle](), [modules]() ### AI overview Square's Mobile Developer Experience Android team reports that applying software engineering best practices and incremental improvements to build logic produced durable gains as the Point of Sale repository grew. The article argues against relying on risky "silver bullet" solutions. ### Source excerpt The data-driven case for best practices and against silver bullets ## Miro Threat Modeling Template for EoP DevFeed: [Miro Threat Modeling Template for EoP]() Original publisher: [Read original article]() Author: Brett Crawley Published: 2022-11-10T00:00:00Z Content type: tutorial Language: en Sources: [Shostack & Friends Blog]() Topics: [Template](), [Requirements](), [repo]() Tags: [repo](), [requirements](), [template](), [version]() ### AI overview This guest post explains how to use a Miro template to run the Elevation of Privilege threat-modeling card game remotely. It covers team composition, required architecture and requirements diagrams, board setup, and documenting exported threat models alongside application code. ### Source excerpt A Miro template for Elevation of Privilege ## Ubuntu - Key is stored in legacy trusted.gpg keyring... DevFeed: [Ubuntu - Key is stored in legacy trusted.gpg keyring...]() Original publisher: [Read original article]() Author: Tom Published: 2022-10-21T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Ubuntu](), [legacy](), [repo](), [ASCII]() Tags: [apt-key-deprecation](), [ascii](), [debian](), [how-to](), [legacy](), [legacy-trusted-gpg-keyring](), [linux](), [managing-gpg-keys-ubuntu](), [repositories](), [repository-key-management](), [ubuntu](), [ubuntu-22-04-warnings](), [ubuntu-gpg-keyring](), [verify]() ### AI overview A tutorial explains why Ubuntu 22.04 warns that a key is stored in the legacy trusted.gpg keyring and describes how to manage repository GPG keys separately. ### Source excerpt Learn how to resolve the "Key is stored in legacy trusted.gpg keyring" warning on Ubuntu 22.04 by properly managing GPG keys for repositories. ## Deprecating Marvin DevFeed: [Deprecating Marvin]() Original publisher: [Read original article]() Author: Stanko Published: 2020-09-16T00:00:00Z Content type: opinion Language: en Sources: [Stanko Tadić]() Topics: [Boilerplate](), [React](), [repo](), [maintenance]() Tags: [boilerplate](), [maintenance](), [react](), [repo](), [software]() ### AI overview The author announces the deprecation of Marvin, a React project boilerplate created for personal needs that later became an internal project and was used by thousands of people. The repository will remain available, but further improvements and maintenance will stop because the evolving React ecosystem made maintaining a single boilerplate unproductive. ### Source excerpt It is funny, I would never say I would be sad to deprecate a software project. Especially a project boilerplate. But I just merged the deprecation notice, and I do feel down a little. I created Marvin about four years ago for my own needs. Since then it grew, became internal project at Work&CoFun fact, our website is made on top of Marvin. and was used by thousands of people. Why? # When Marvin was created React landscape was looking a lot different than today. The ecosystem continues to relentlessly evolve and maintaining a single boilerplate to capture all these possibilities has become unproductive. The repo will stay available, but we are stopping further improvements and maintenance. Thank you! # A big thank you to everyone who used and supported Marvin! ## Adding Staticman Comments DevFeed: [Adding Staticman Comments]() Original publisher: [Read original article]() Author: Travis Downs (travis.downs@gmail.com) Published: 2020-02-05T00:00:00Z Content type: tutorial Language: en Sources: [Performance Matters]() Topics: [GitHub](), [GitHub Pages](), [Bot](), [Pull Request](), [Heroku](), [personal access token](), [hosting](), [repo]() Tags: [blog](), [file](), [github](), [github-pages](), [guide](), [heroku](), [hosting](), [meta](), [personal-access-token](), [pull-request](), [static-site](), [staticman]() ### AI overview A tutorial explaining how to add Staticman comments to a static blog. It covers the submission flow, deploying the API bridge on Heroku, using GitHub pull requests to store comments, and republishing through GitHub Pages. ### Source excerpt Adding static comments to a static blog using staticman. Static. ## Jumpstart Rails Tutorial 01 - Bringing an Existing Codebase In DevFeed: [Jumpstart Rails Tutorial 01 - Bringing an Existing Codebase In]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-01-02T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Tutorial](), [repo](), [Code](), [Deployment](), [Databases](), [Yarn](), [GitHub]() Tags: [code](), [database](), [deployment](), [development](), [getting-started](), [github](), [how-to](), [jumpstart](), [rails](), [repo](), [tutorial]() ### AI overview This tutorial series documents porting an existing Rails application into the Jumpstart Rails application framework. The first article covers cloning the licensed repository, installing dependencies with Yarn, updating database.yml, and adding the local codebase to GitHub. ### Source excerpt Updated: 5/5/2020 It is the second day of the New Year - welcome to 2020 - and I have still failed to launch my side project that I started midway through 2019. Sigh. I find myself fundamentally regretting this but, well, life: New Job Wife in Hospital Son and Schooling Issues Etc So my New Year's Resolution(s) is: Launch by end of Q1, 2020 Not have deployment eat my brain Launch with Something that I'm Visually Proud Of Launch with SAAS billing features from day 1 and Get paying Customers That last item, SAAS billing features, is a sticky point. I've actually implemented this myself before - I wrote all the back end code for the AppData SAAS engine which successfully processed over 3.1 million dollars in revenue over a 5 year period (BrainTree api). And I really, really, really don't want to rewrite that. Nor do I want to use a third party service and lose another percentage chunk over baseline Stripe fees. And all of this means that I need to use the Jumpstart Rails application framework. I already have a license for it anyway and the issue is that I need to port an existing, almost complete Rails app into it. All of the blog posts starting with Jumpstart Rails Tutorial nn will cover this process. While there is good documentation for Jumpstart Rails, it is reference material rather than how to material. Note: If anything I write during this series comes off as critical of Chris Oliver, the man behind Jumpstart Rails, it isn't. I am an unabashed fan of the damn fine work that Chris Oliver does. Step 1 - Getting Started with Jumpstart Rails - Clone the Repo The first step is to purchase an actual license for Jumpstart Rails. This will get you added onto the Jumpstart Rails git repo: https://gitlab.com/gorails/jumpstart-pro What you need to do is begin by cloning this repo down to your local system: git clone git@gitlab.com:gorails/jumpstart-pro.git web_change_me_now2 You notice that I changed the name of this to: web_change_me_now2 I changed it since my previous re ## Updating to the Latest Version of JumpStart Pro DevFeed: [Updating to the Latest Version of JumpStart Pro]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2019-12-29T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Git](), [GitLab](), [Rails](), [repo](), [GitHub](), [Development]() Tags: [development](), [git](), [github](), [gitlab](), [jumpstart](), [rails](), [repo]() ### AI overview A tutorial on updating JumpStart Pro projects by cloning the source repository, configuring separate remotes, and pushing project changes. It explains how copying a project without its .git directory disconnected the project from the original remote and prevented normal updates. ### Source excerpt So I've been using JumpStart Pro to build a new side project and in a discussion with Chris Oliver, the creator of JumpStart Pro, I reported a bug which he said "Oh - you should update to the latest". He viewed the update process as something seamless and I, honestly, didn't get it. And, in researching this, I discovered that I made a fatal mistake. The rest of this blog post covers that mistake and explains how you update JumpStart Pro. Here's the tldr (too long; did not read): ALWAYS, ALWAYS, ALWAYS create a new app based on JumpStart Pro by cloning it from the GitLab source i.e. you start with: "git clone git@gitlab.com:gorails/jumpstart-pro.git YOUR_PROJECT_NAME" Go to github and create a repo for YOUR_PROJECT_NAME Copy the github clone info and add it as a separate remote: git remote add YOUR_PROJECT_NAME git@github.com:YOUR_GITHUB_USERNAME/YOUR_PROJECT_NAME.git Make a change like updating the README.md and do the add / commit dance and push to your repo as git push YOUR_PROJECT_NAME master Even though I've worked with Git for more than a decade now, I've previously only worked with Heroku as a git remote so I missed the implications of this when I originally cloned my first JumpStart Pro app. Sigh. The critical mistake I made was that I had started my second JumpStart Pro project by copying from the first JumpStart Pro project I had made and the NOT moving over the .git folder. This meant that my new project was now disconnected from the original remote so I couldn't just do a git pull to update it. Fixing My Own Stupidity Here's what I did to fix this: I started by creating a new application cloning into a new location: git clone git@gitlab.com:gorails/jumpstart-pro.git okrsnow I created a new git repo for my app I added the new repo with: git remote add okrsnow git@github.com:fuzzygroup/okrsnow.git I made a change and pushed to git push okrsnow master I manually copied over all the code from my original JumpStart pro repo. Given that Rails apps have such a c ## Cleanup old GitHub Forks DevFeed: [Cleanup old GitHub Forks]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2018-06-02T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [GitHub](), [repo](), [export]() Tags: [github](), [install](), [linux](), [macos](), [repositories](), [token]() ### AI overview A tutorial on using the fork-cleaner tool to identify and delete unused GitHub forks. It checks for forks, stars, dependencies, open pull requests, and recent activity, with options to customize inactivity thresholds, blacklist repositories, and include private forks. ### Source excerpt I like to keep my GitHub clean. I delete forks I'm not using anymore, move old abandoned repositories to my graveyard and etc. [Next page]()