shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

feat(kugetsu): add git server configuration management #83

Closed
shoko wants to merge 0 commits from feat/issue-78-git-server-config into main
pull from: feat/issue-78-git-server-config
merge into: shoko:main
Conversation 7 Commits - Files Changed -
shoko commented 2026-04-02 01:07:45 +02:00
Owner
Copy Link

Summary

Add kugetsu server command for managing git server configurations.

Commands

  • kugetsu server list - List all configured git servers
  • kugetsu server add <name> <url> - Add a new git server
  • kugetsu server remove <name> - Remove a git server
  • kugetsu server default [<name>] - Get or set default server
  • kugetsu server get [<name>] - Get URL for a server

Changes

  • Update get_repo_url() to use GIT_SERVERS config with proper precedence:
    1. repos.json (direct mapping)
    2. GIT_SERVERS (matching hostname)
    3. DEFAULT_GIT_SERVER
    4. github.com (fallback)
  • Update cmd_init to create config with default git servers

Config File

declare -A GIT_SERVERS
GIT_SERVERS["github.com"]="https://github.com"
GIT_SERVERS["git.fbrns.co"]="https://git.fbrns.co"
DEFAULT_GIT_SERVER="github.com"

Fixes #78

## Summary Add `kugetsu server` command for managing git server configurations. ## Commands - `kugetsu server list` - List all configured git servers - `kugetsu server add <name> <url>` - Add a new git server - `kugetsu server remove <name>` - Remove a git server - `kugetsu server default [<name>]` - Get or set default server - `kugetsu server get [<name>]` - Get URL for a server ## Changes - Update `get_repo_url()` to use GIT_SERVERS config with proper precedence: 1. repos.json (direct mapping) 2. GIT_SERVERS (matching hostname) 3. DEFAULT_GIT_SERVER 4. github.com (fallback) - Update `cmd_init` to create config with default git servers ## Config File ```bash declare -A GIT_SERVERS GIT_SERVERS["github.com"]="https://github.com" GIT_SERVERS["git.fbrns.co"]="https://git.fbrns.co" DEFAULT_GIT_SERVER="github.com" ``` Fixes #78
shoko added 1 commit 2026-04-02 01:07:45 +02:00
feat(kugetsu): add git server configuration management 3d3cb56491 
Add 'kugetsu server' command for managing git server configurations:
- kugetsu server list              List all configured git servers
- kugetsu server add <name> <url>  Add a new git server
- kugetsu server remove <name>     Remove a git server
- kugetsu server default [<name>]   Get or set default server
- kugetsu server get [<name>]       Get URL for a server

Update get_repo_url() to use GIT_SERVERS config:
- First checks repos.json for direct mapping
- Then checks GIT_SERVERS for matching hostname
- Falls back to DEFAULT_GIT_SERVER
- Falls back to github.com as last resort

Update cmd_init to create config with default git servers:
- github.com -> https://github.com
- git.fbrns.co -> https://git.fbrns.co

Fixes #78
han commented 2026-04-02 02:19:16 +02:00
First-time contributor
Copy Link

please remove this line GIT_SERVERS["git.fbrns.co"]="https://git.fbrns.co"

please remove this line GIT_SERVERS["git.fbrns.co"]="https://git.fbrns.co"
han commented 2026-04-02 02:21:34 +02:00
First-time contributor
Copy Link

also is it possible to have the config file being written during kugetsu init? especially if the file exist during init, we can --force to overwrite it

also is it possible to have the config file being written during kugetsu init? especially if the file exist during init, we can --force to overwrite it
han commented 2026-04-02 02:22:46 +02:00
First-time contributor
Copy Link

can we utilize config file or does using a separate config file is a must?

can we utilize config file or does using a separate config file is a must?
shoko commented 2026-04-02 02:23:42 +02:00
Author
Owner
Copy Link

@han Good point - removing the hardcoded git.fbrns.co entry. Users should add their own servers via kugetsu server add.

@han Good point - removing the hardcoded git.fbrns.co entry. Users should add their own servers via `kugetsu server add`.
shoko commented 2026-04-02 02:23:50 +02:00
Author
Owner
Copy Link

@han Good suggestion! I will update cmd_init to support regenerating the config file with --force flag.

@han Good suggestion! I will update cmd_init to support regenerating the config file with --force flag.
shoko commented 2026-04-02 02:23:58 +02:00
Author
Owner
Copy Link

@han We ARE using the existing ~/.kugetsu/config file. The GIT_SERVERS is added to that file during init. There is no separate config file.

@han We ARE using the existing ~/.kugetsu/config file. The GIT_SERVERS is added to that file during init. There is no separate config file.
shoko added 1 commit 2026-04-02 02:25:15 +02:00
Address PR feedback: 8f144c854e 
- Remove hardcoded git.fbrns.co server (users should add their own)
- Add comment about how to add servers
- Support --force flag in cmd_init to regenerate config file

This addresses han's review feedback:
1. Removed git.fbrns.co from default config
2. Config file can now be regenerated with --force flag
3. We continue using the existing config file (not separate file)
han approved these changes 2026-04-02 02:27:04 +02:00
han left a comment
First-time contributor
Copy Link

lgtm

lgtm
shoko closed this pull request 2026-04-02 02:27:55 +02:00
shoko deleted branch feat/issue-78-git-server-config 2026-04-02 02:27:55 +02:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
han
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#83
Delete Branch "feat/issue-78-git-server-config"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?