robert/gt-tool
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects 1 Releases 5 Wiki Activity

Add inference for repository name #8

New Issue
Closed
opened 2025-07-06 11:29:45 -07:00 by robert · 1 comment
robert commented 2025-07-06 11:29:45 -07:00
Owner
Copy Link

The repository name is usually the same on the server as it is on the local filesystem. Similarly, the current working directory will often be the project root or a subfolder. I can scan upwards for a git repo and use that folder as the default repository name.

I won't have the GTTOOL_GITEA_FQRN without the username, though, and system account names aren't likely to match Gitea account names. I'll need a global and/or per-user config file to supply that.

The repository name is usually the same on the server as it is on the local filesystem. Similarly, the current working directory will often be the project root or a subfolder. I can scan upwards for a git repo and use that folder as the default repository name. I won't have the GTTOOL_GITEA_FQRN without the username, though, and system account names aren't likely to match Gitea account names. I'll need a global and/or per-user config file to supply that.
robert added the Kind/Feature label 2025-07-06 11:29:45 -07:00
robert added this to the Configuration & Heuristics project 2025-07-06 15:00:46 -07:00
robert moved this to To Do in Configuration & Heuristics on 2025-07-21 11:47:39 -07:00
robert moved this to Done in Configuration & Heuristics on 2025-07-21 14:23:11 -07:00
robert commented 2025-07-21 14:31:03 -07:00
Author
Owner
Copy Link

Basic repo name inference was completed in da8f008f1a.

The program will use the current dir as the repo name if it is not on the CLI, environment, or a config file.

Basic repo name inference was completed in da8f008f1a4e342a98cf213adf85128346e469bf. The program will use the current dir as the repo name if it is not on the CLI, environment, or a config file.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label Kind/Feature
Milestone
No items
No Milestone
Projects
Clear projects
No project Configuration & Heuristics
Assignees
Clear assignees
jamis robert
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: robert/gt-tool#8
Delete Branch "%!s()"

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?