# Repositories Published articles for Repositories. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot Git repositories now on Codeberg (RIP Notabug) DevFeed: [Libreboot Git repositories now on Codeberg (RIP Notabug)]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [forgejo](), [Git](), [ci](), [pull-requests](), [Gitea]() Tags: [bios](), [canoeboot](), [ci](), [coreboot](), [forgejo](), [free-software](), [git](), [go](), [libre](), [libreboot](), [opensource](), [pull-requests](), [repositories](), [uefi]() ### AI overview Libreboot is moving its advertised Git repositories to Codeberg because Notabug has become unreliable and frequently returns HTTP 500 errors. Notabug remains available as a backup, while Codeberg provides features including issue search and built-in CI through Woodpecker. ### Source excerpt Article: Libreboot Git repositories now on Codeberg (RIP Notabug) Web link: https://libreboot.org/news/codeberg.html ## Libreboot mailing list and git mirror now available on sourcehut (sr.ht) DevFeed: [Libreboot mailing list and git mirror now available on sourcehut (sr.ht)]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [hosting](), [forgejo](), [RSS Feed]() Tags: [bios](), [canoeboot](), [coreboot](), [forgejo](), [free-software](), [libre](), [libreboot](), [mirror](), [opensource](), [repositories](), [rss](), [uefi]() ### AI overview Libreboot has added git hosting on SourceHut for the lbmk and lbwww repositories. The project also has a mailing list for patches, announcements, and questions, while Codeberg remains the main provider for patches. ### Source excerpt Article: Libreboot mailing list and git mirror now available on sourcehut (sr.ht) Web link: https://libreboot.org/news/sourcehut.html ## New Git repositories added as backup Libreboot mirrors DevFeed: [New Git repositories added as backup Libreboot mirrors]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [Git](), [libreboot](), [coreboot]() Tags: [article](), [backup](), [bios](), [canoeboot](), [coreboot](), [free-software](), [git](), [libre](), [libreboot](), [news](), [opensource](), [repositories](), [uefi]() ### AI overview Libreboot announces official mirrors for its Git repository on additional hosting platforms. The mirrors back up the main Codeberg mirror and include the lbmk build system and lbwww website files, with more mirrors planned. ### Source excerpt Article: New Git repositories added as backup Libreboot mirrors Web link: https://libreboot.org/news/mirrors.html ## Cellular Network Infrastructure - Removal of binary package feeds for Debian 11 (bullseye) DevFeed: [Cellular Network Infrastructure - Removal of binary package feeds for Debian 11 (bullseye)]() Original publisher: [Read original article]() Author: osmith Published: 2026-09-07T13:01:53Z Content type: news Language: en Sources: [Open Source Mobile Communications: News]() Topics: [Debian]() Tags: [2026](), [bug](), [debian](), [end-of-life](), [issue](), [os](), [packages](), [repositories](), [tracker]() ### AI overview Osmocom plans to stop building binary packages for Debian 11 in its repositories on December 7, 2026, because Debian 11 has reached end of life. Customers needing continued access can contact sysmocom about commercial long-term support. ### Source excerpt Debian 11 has reached its End Of Life. We plan to stop building Osmocom packages for it in our binary package repositories in three months (2026-12-07). If you are still continue to require Debian 11 binary packages, please contact sales sysmocom.de to discuss commercial terms for long-term support. ## How a medical database developed at MIT evolved into a global standard of data-sharing DevFeed: [How a medical database developed at MIT evolved into a global standard of data-sharing]() Original publisher: [Read original article]() Author: Emma Foehringer Merchant | Institute for Medical Engineering and Science Published: 2026-07-29T14:00:00Z Content type: news Language: en Sources: [MIT AI News]() Topics: [data](), [Database](), [datasets]() Tags: [academic](), [artificial-intelligence](), [data](), [database](), [electrical-engineering-and-computer-science-eecs](), [global-data-sharing](), [harvard-mit-health-sciences-and-technology](), [harvard-mit-health-sciences-and-technology-hst](), [health](), [health-care](), [health-data-nexus](), [health-sciences-and-technology](), [history](), [history-of-mit](), [history-of-science](), [history-of-science-and-technology](), [information-systems](), [institute-for-medical-engineering-and-science-imes](), [internet](), [medical-data-sharing](), [medicine](), [mimic-medical-information-marked-for-intensive-care](), [mit-imes](), [mit-rle](), [physionet](), [repositories](), [research](), [research-laboratory-of-electronics](), [school-of-engineering](), [science](), [thomas-heldt](), [tom-pollard]() ### AI overview An MIT-developed collection of digitized electrocardiogram recordings became the foundation of PhysioNet, a global repository for biomedical and clinical data. The platform now hosts hundreds of databases and supports research users worldwide. ### Source excerpt The visionary PhysioNet platform launched 25 years ago, based on a system developed at MIT in the 1970s. It has become one of the most comprehensive biomedical and clinical data repositories in existence. ## Reducing Project and Personal Commitments After Becoming a Parent DevFeed: [Reducing Project and Personal Commitments After Becoming a Parent]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2026-07-07T03:00:00Z Content type: opinion Language: en Sources: [Carlos Becker]() Topics: [Less](), [Repositories](), [Code]() Tags: [archiving](), [code](), [less](), [repositories]() ### AI overview The author reflects on simplifying life after the birth of his daughter. He archives personal repositories and steps back from some commitments to reduce notifications and mental load while keeping activities he deeply enjoys. ### Source excerpt My daughter was born, and I did, in fact, manage to do less. ## Fedora Documentation translations again available DevFeed: [Fedora Documentation translations again available]() Original publisher: [Read original article]() Author: peartown Published: 2026-06-26T09:19:27Z Content type: release Language: en Sources: [Fedora Community Blog]() Topics: [Fedora](), [Documentation](), [migration](), [Tool]() Tags: [blog](), [documentation](), [fedora-project-community](), [forge](), [localization-l10n](), [migration](), [post](), [repositories](), [tools](), [updates]() ### AI overview Updates to Fedora Documentation translations are available again after the translation repositories and necessary tools were migrated from Pagure to the Fedora Forge. ### Source excerpt Updates to translations of Fedora Documentation are again available. As announced on March 3rd, the unavailability of translation updates was due to the migration of the translation repositories and necessary tools from Pagure to the Fedora Forge. It took longer than expected but we are pleased to report this undertaking came finally to the end. The post Fedora Documentation translations again available appeared first on Fedora Community Blog. ## Unsubscribe from a GitHub organization DevFeed: [Unsubscribe from a GitHub organization]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2026-05-20T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [GitHub](), [pull-requests](), [notifications](), [Shell](), [Script](), [Open Source]() Tags: [github](), [notifications](), [open-source](), [pull-requests](), [repositories](), [script](), [shell]() ### AI overview A short tip explains that leaving a GitHub organization does not stop notifications from open-repository issues and pull requests. The author used a shell script to unsubscribe from those items and close remaining open pull requests. ### Source excerpt Just leaving the organization is not enough. ## AI Code Generation Is Fueling Disposable Software Projects DevFeed: [AI Code Generation Is Fueling Disposable Software Projects]() Original publisher: [Read original article]() Author: Mike Yerou Published: 2026-04-21T14:10:12Z Content type: opinion Language: en Sources: [Rock and Null]() Topics: [AI-assisted coding](), [Maintainers](), [Software](), [Library](), [Tool]() Tags: [ai](), [artificial-intelligence](), [code-generation](), [disposable-software](), [maintainers](), [repositories](), [risk](), [software-engineering](), [thoughts]() ### AI overview AI code generation makes it possible to turn ideas into software quickly, but it may also encourage projects that are abandoned soon after creation. The article argues that maintainers' track records should be considered when evaluating libraries and tools. ### Source excerpt AI allows us to ship software instantly, but it's also fueling a surge of "disposable" projects. The team behind the code matters more than the code itself in the age of AI generation. ## How to Query GitHub for User Contributions in a Specific Timeframe DevFeed: [How to Query GitHub for User Contributions in a Specific Timeframe]() Original publisher: [Read original article]() Author: Chris Hager Published: 2025-10-10T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [GitHub](), [GraphQL](), [GitHub API]() Tags: [api](), [contributions](), [github](), [graphql](), [how-to](), [query](), [repositories](), [timeframe](), [tracking]() ### AI overview A tutorial showing how to use the GitHub GraphQL API to list public repositories a user contributed to during a specified timeframe, with an optional modification to include commit counts and format the output. ### Source excerpt I needed needed to find all public GitHub repositories a user has contributed to within a specific timeframe, and wanted to share - and record for myself - the API query I learned. This can be a useful for generating reports, tracking progress, analyzing activity over a certain period, and more. Use the GitHub GraphQL API We leverage the GitHub GraphQL API to get the list of public repositories a user contributed to within a specific timeframe, using the contributionsCollection field to specify a time range and retrieve contributions made by a user during that period. ## What Should Repositories Return in Domain-Driven Design? DevFeed: [What Should Repositories Return in Domain-Driven Design?]() Original publisher: [Read original article]() Author: Furkan Kolcu Published: 2025-09-09T16:41:47Z Content type: article Language: en Sources: [Furkan Kolcu - Software Engineer Blog]() Topics: [Domain-driven design (DDD)](), [Repositories](), [Persistence]() Tags: [aggregates](), [clean-architecture](), [design-patterns](), [domain-driven-design](), [domain-driven-design-ddd](), [examples](), [lightweight](), [practical](), [repositories](), [repository-pattern](), [software-architecture](), [software-engineering](), [technology]() ### AI overview This article examines what repositories should return in Domain-Driven Design. It compares aggregates, DTOs or arrays, and primitives or special results, concluding that repositories should return aggregates when domain behavior is needed and primitives when they express valid domain-level answers. ### Source excerpt Repositories are a core part of Domain-Driven Design, but what they should return is often debated. Should it be aggregates, DTOs, or simple values? In this post, I share practical guidelines, examples, and tradeoffs to help clarify how to keep repositories focused on serving the domain. ## Here and Now: Reusing Code at Feedzai with JupyterLab Snippets DevFeed: [Here and Now: Reusing Code at Feedzai with JupyterLab Snippets]() Original publisher: [Read original article]() Author: João Palmeiro Published: 2025-03-17T13:11:26Z Content type: article Language: en Sources: [Feedzai]() Topics: [jupyterlab](), [Data Science](), [Code](), [Data analysis]() Tags: [code](), [data-analysis](), [data-science](), [debugging](), [jupyter](), [jupyterlab](), [python](), [repositories](), [snippet]() ### AI overview Feedzai developed JupyterLab Snippets to help data scientists reuse code from the many notebooks created for daily work. The article describes research using notebook repository statistics and user interviews, and reports that duplicating notebooks, maintaining reference collections of snippets, and sharing notebooks or snippets are common practices. ### Source excerpt Data scientists use different Jupyter notebooks every day -- ranging from disposable ones for quick tasks to those shareable with clients. Over time, more and more notebooks accumulate, making it increasingly difficult to reuse them in whole or in part. To mitigate this problem and make the most relevant pieces of code quickly accessible to every data scientist, we developed JupyterLab Snippets at Feedzai -- our take on leveraging code snippets directly on JupyterLab. JupyterLab is a computational notebook platform that enables us to carry on data science work (and beyond) via notebooks. These notebooks, where code, text, and images come together, allow us to complete all kinds of tasks, keeping each input close to each output. At Feedzai, data scientists have access to different JupyterLab environments packed with custom notebooks and Python packages. Here they go from analyzing data to training models, from preparing reports to debugging the system -- a "lab of all trades", we could say. Given the importance of JupyterLab and notebooks in the daily work of our data scientists, we started a research project that culminated in JupyterLab Snippets. First, we collected statistics from internal notebook repositories across teams and conducted user interviews with junior and senior data scientists. We needed to know more about how data scientists actually use JupyterLab and notebooks, and what their ideas are for a better platform. A sneak peek of JupyterLab Snippets. From the very start, every data scientist can import snippets immediately or start their collection by creating one from scratch. After compiling the insights, several aspects became clear: JupyterLab and notebooks are heavily used for all sorts of data science and ad-hoc tasks (typically one per notebook). There is no single type of task (e.g., exploratory data analysis) that is more commonly addressed with notebooks than others. While file structures may look similar at first glance (each environment has at ## Automatically merge dependabot pull requests DevFeed: [Automatically merge dependabot pull requests]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2024-12-11T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [GitHub Actions](), [Dependabot](), [Automation](), [pull-requests](), [GitHub]() Tags: [automation](), [dependabot](), [github](), [github-actions](), [pull-requests](), [repositories]() ### AI overview The article describes an automation that approves and merges Dependabot pull requests after a successful build. It requires enabling the GitHub Actions permission to create and approve pull requests in each repository. ### Source excerpt A couple of weeks ago I added a small automation to automatically merge dependabot pull requests if the build succeed. ## Making the most of GitHub Code Search DevFeed: [Making the most of GitHub Code Search]() Original publisher: [Read original article]() Published: 2023-09-30T00:00:00Z Content type: tutorial Language: en Sources: [Arkadiusz Chmura]() Topics: [code search](), [GitHub](), [Code](), [syntax](), [Sorting]() Tags: [code-search](), [github](), [regular-expressions](), [repositories](), [search](), [sorting](), [syntax]() ### AI overview A practical guide to GitHub Code Search, covering exact-string searches, Boolean expressions, regular expressions, qualifiers, result limits, sorting behavior, and indexing limitations. It also presents the tool as useful for code exploration and learning. ### Source excerpt The new search engine offers powerful code searching mechanisms we can leverage for quickly finding the code we need, as well as for exploration and learning. ## 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. ## The Second Best Way to Fetch a Spring Data JPA DTO Projection DevFeed: [The Second Best Way to Fetch a Spring Data JPA DTO Projection]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-08-30T14:48:44Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Code](), [Spring Boot]() Tags: [code](), [dto-projection](), [jooq](), [jooq-in-use](), [nested-collections](), [repositories](), [spring-boot](), [spring-data-jpa]() ### AI overview The article presents jOOQ as a second way to implement a Spring Data JPA DTO projection. It shows value-constructor and aggregate-function approaches, emphasizing type-safe record conversion and reduced infrastructure code. ### Source excerpt I've just stumbled upon this great post by Vlad Mihalcea, titled The Best Way to Fetch a Spring Data JPA DTO Projection. It got some nice traction on reddit, too. This is such a nice use-case and apt solution, I wanted to quickly show the second best way of doing the same, with jOOQ this ... Continue reading The Second Best Way to Fetch a Spring Data JPA DTO Projection -> ## Build Your Own Content Management System (CMS) From a Template DevFeed: [Build Your Own Content Management System (CMS) From a Template]() Original publisher: [Read original article]() Author: Tim McCallum Published: 2022-08-26T19:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Content Management System](), [Template]() Tags: [blog](), [blog-post](), [build](), [cms](), [content](), [files](), [generate](), [how-to](), [management](), [needs](), [repositories](), [repository](), [running](), [structure](), [templates]() ### AI overview This tutorial explains how repository templates can be used to generate a content management system with a consistent directory structure, branches, and files, which can then be customized. ### Source excerpt Repository templates allow you and others to generate new repositories with the same directory structure, branches, and files. This blog post shows you how to build your own CMS from a template. The process is very quick and once up and running you can go ahead and customize your CMS to meet your needs. ## This month in Mobian: May 2022 DevFeed: [This month in Mobian: May 2022]() Original publisher: [Read original article]() Author: Mobian team Published: 2022-05-31T23:59:59Z Content type: article Language: en Sources: [Mobian's Blog]() Topics: [Development](), [GitLab](), [ci](), [Debian](), [Kernel](), [systemd](), [Wiki]() Tags: [blog-posts](), [bugs](), [ci](), [configs](), [debian](), [gitlab](), [kernel](), [kernels](), [repositories](), [systemd](), [update](), [wiki]() ### AI overview A May 2022 Mobian development update covers monthly developer meetings, planned repository and developer-wiki moves toward Debian infrastructure, kernel and audio fixes, universal images for PinePhone devices, tow-boot limitations on PineTab, and a PinePhone Keyboard driver change. ### Source excerpt This is the first in a (hopefully) series of short blog posts summarizing what has happened in Mobianland. Given that Mobian integrates much of the ecosystem not developed by us, this report could reiterate many of the things being said somewhere else. Monthly dev meeting Despite being located all over the world (really!), we manage to meet in person once a month. Well, ok, "meet in person" means we conduct a jitsi video call. It is fun seeing all these sleepy faces where half of the people would like to go to bed already, while others wished they could have remained in bed longer. The TL;DR: we will attempt to move over more repositories from gitlab to salsa.debian.org (given gitlabs changes to the CI allowance we get, and in an attempt to align ourselves closer to Debian). In a similar move, the developer's wiki (NOT the user wiki) moves over to the Debian wiki. pondering if systemd-repart and systemd-growfs can maybe replace "growroot" We really should be opening a user-contrib section or something where contributed ports and kernels can live, e.g. for the Nexus 5. Planning stage. OnePlus 6 / Pocophone F1 Audio was broken due to a missing config option on 5.17 kernels, and was fixed by a subsequent update. Thanks to everyone who reported this issue and provided the information allowing us to fix it. Universal Images We have a universal mobian image that boots on the original Pinephone and the Pinephone Pro, however, there are still some bugs to iron out and kernel configs to be adapted. But overall, this looks promising. However, this will require some tool that can adapt configuration settings at runtime, based on the device it is currently running on. Tow-boot We were one of the earliest distributions to move over to tow-boot, and that worked out nearly well. However, there is a little catch: There is no tow-boot for the PineTab yet. So all images post-March 27, will not be able to install a U-boot if you have non installed yet. Help to port tow-boot to the Pin ## Safer Internet Day and Open Source Codes of Conduct DevFeed: [Safer Internet Day and Open Source Codes of Conduct]() Original publisher: [Read original article]() Author: Sarah Graywood Published: 2022-02-14T17:23:51Z Content type: article Language: en Sources: [Flickr]() Topics: [Open Source](), [GitHub]() Tags: [code-of-conduct](), [community](), [contributions](), [contributors](), [developers](), [github](), [internet](), [open-source](), [repositories]() ### AI overview Flickr describes adding a code of conduct to its most trafficked open-source repositories on GitHub as part of its Safer Internet Day efforts. The article explains how codes of conduct establish expectations for developer interactions and support safer, more inclusive communities. ### Source excerpt To continue the work of making our spaces safer and more accessible to all, we have added a code of conduct to our most trafficked open source repositories on GitHub in celebration of Safer Internet Day! Continue reading -> ## Inclusive Language Updates DevFeed: [Inclusive Language Updates]() Original publisher: [Read original article]() Author: Remind Published: 2022-01-21T00:00:00Z Content type: article Language: en Sources: [Remind]() Topics: [systems](), [GitHub](), [Databases]() Tags: [databases](), [engineering](), [github](), [inclusive](), [postgresql](), [repositories]() ### AI overview Remind's Sustaining Engineering team describes updates to inclusive language across its codebases, including changing GitHub's default branch from master to main and replacing master/slave and whitelist/blacklist terminology with writer/reader and allowlist/blocklist. ### Source excerpt Inclusive Language Overview The Sustaining Engineering team at Remind recently implemented changes that focus on using inclusive language within our codebases. We encourage other engineering teams to do the same, and hope these updates create a more inclusive space for everyone at Remind. Terms like master and slave have no place in a modern codebase. They don't belong inside of our repositories, and they certainly do not belong on a repository's default branch on GitHub. At Remind, we have 59 distinct services that power our application. Each of these services has language that needs to be updated thoughtfully and intentionally to ensure that our systems remain available to the parents, teachers, and students that depend on them. We followed the lead of Indeed's VP of Engineering Jack Humphrey to identify and replace problematic language with the help of this blog post. We also had a number of internal conversations between team members that helped us iterate on the language that we intended to change, which worked specifically for our teams at Remind. Hopefully, outlining the changes that we made can serve to help other organizations working to make their workplaces more inclusive. Actions We're Taking We've committed ourselves to the following updates: Github default branch master " main Database Terminology Master/Slave -> Writer/Reader Permission Lists Whitelist/Blacklist -> Allowlist/Blocklist I began our updates within three of the services that my team - Sustaining Engineering - owns and operates within regularly. The steps that I took to update each of these repositories are as follows: Checked the repo for hard coded references to master branch and changed to main locally Checked across all repos at Remind for hard coded references to the master branch of the repo I was currently working to update Checked the repo for master and slave terminology, generally related to databases and updated with writer and reader This was updated from source and replica to ## Publishing Android libraries to MavenCentral in 2021 DevFeed: [Publishing Android libraries to MavenCentral in 2021]() Original publisher: [Read original article]() Author: Márton Braun Published: 2021-02-04T16:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [Library](), [Maven](), [Gradle](), [GitHub Actions](), [API]() Tags: [android](), [bintray](), [ci](), [github](), [github-actions](), [gradle](), [guide](), [how-to](), [integrity](), [libraries](), [maven-repository](), [mavencentral](), [release](), [repositories](), [signing](), [sonatype](), [tutorials]() ### AI overview A step-by-step, updated guide to publishing Android and other libraries to MavenCentral in 2021. It covers Gradle publishing, GPG signing, Sonatype infrastructure, Maven publishing plugins, and GitHub Actions CI, with context on JitPack and JCenter. ### Source excerpt MavenCentral is the place to be for Android libraries, but publishing there is no easy task. With JCenter going away soon, this problem is more timely than ever. Here's the step-by-step guide on how to do it. ## Publishing an Android library to MavenCentral in 2019 DevFeed: [Publishing an Android library to MavenCentral in 2019]() Original publisher: [Read original article]() Author: Márton Braun Published: 2019-08-27T16:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [Android Library](), [Android](), [Maven](), [Library](), [Publishing]() Tags: [android](), [android-library](), [dependencies](), [gradle](), [integrity](), [library](), [maven](), [mavencentral](), [pair](), [private-key](), [publication](), [repositories]() ### AI overview A tutorial explaining how to publish an Android library to MavenCentral, including Sonatype registration, artifact signing with a GPG key pair, and the publication workflow. ### Source excerpt MavenCental is the place to be for serious libraries, but setting up publication to it can be a truly daunting task. Here's the guide to how we do it. ## Managing Git configurations DevFeed: [Managing Git configurations]() Original publisher: [Read original article]() Author: Márton Braun Published: 2019-02-25T18:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [Git](), [configuration](), [Command-line interface]() Tags: [android](), [command-line](), [configuration](), [credentials](), [git](), [kotlin](), [marton-braun](), [repositories](), [signing](), [zsmb](), [zsmb-co](), [zsmb13](), [zsmbco]() ### AI overview This tutorial explains how to manage Git configurations when using different credentials across work, school, personal, or client repositories. It compares a single global configuration with a global configuration supplemented by per-repository local overrides, and discusses commit signing settings. ### Source excerpt We all use different git configurations for various reasons, and it's easy to get them mixed up. Here's a look at some ways of managing them better. ## 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]()