danielmiessler / danielmiessler/LifeOS

Feature Request: Accept different git backed repositories (not only gh)

Open
#2,070 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
19k
Forks
2.5k
Avg merge
8d 17h
Merged PRs (30d)
1

Description

Currently LIFEOS is hardcoding "gh" as a single git repo style and it could simply change/improve to support self-hosted Gitlab or similar.

Output taken from my local LLM and the options it gave.

I believe we should make it possible to use different gits.

-----

Bun.spawnSync(["gh", "repo", "view", repo, "--json", "visibility,isPrivate"])
// and
gh issue create --label "..." --title "..."

To make it work with GitLab, you have three options:

Option A: Write a gh wrapper script
Create a gh shim that translates GitHub API calls to GitLab REST API calls and put it on your PATH before the real gh. This is the least invasive — LifeOS thinks it's talking to GitHub but your wrapper routes
to GitLab. Feasible because the commands are a finite set (repo view, issue create, issue list, issue edit, pr create).

Option B: Patch the LifeOS source
Replace the gh calls in work-config.ts and WorkSweep.ts with glab equivalents, then redeploy. This persists across upgrades (you just re-patch). More work but cleaner.

Option C: Ask for native GitLab support
Open an issue on the LifeOS repo (https://github.com/danielmiessler/LifeOS) requesting a pluggable work provider. They're open to it — the work-config loader already has a loadWorkConfig() pattern that could
dispatch to a provider.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading work-config.ts and WorkSweep.ts, where the issue identifies hardcoded gh calls, and inspect the loadWorkConfig() pattern mentioned in the report. Define how repository providers should be selected and what existing repo, issue, and pull-request operations must continue to support; done means LifeOS can use a self-hosted GitLab or similar provider without GitHub-only calls.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github, typescript
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.