Comments (5)
Just a note, this could also be handled by tagging bugs with metadata instead of physically shard them on disk.
As with many feature request, I'd like to have more user opinions, to see who need that and for what, to make sure this is actually useful, and to tailor the design to the actual usage.
from git-bug.
Just a note, this could also be handled by tagging bugs with metadata instead of physically shard them on disk.
But then you're losing some the pros of bugs being stored as references in a repo.
E.g. moving bugs around even if you don't have git-bug
available should be as simple as:
$git push remote refs/bugs/*:refs/bugs/*;
# or something like this if it supported pathname based schemes:
$git push remote refs/bugs/[somename]/*:refs/bugs/[someone]/* #
Tags, branches, remotes, notes, essentially all types of refs can be namespaced using pathname schemes. On top of that, the entire .git/refs/*
hierarchy can be namespaced again under refs/namespaces/<somename>/
.
Namespacing is a essential feature to maintain the distributed nature of git.
As it currently stands, git-bug
is working like a centralized bugtracker in reverse.
Let's say someone doesn't like some aspect of git-bug
forks it and starts developing independently. An impartial user can add both repos as remotes and build his own custom version.
Git has no problem supporting this workflow.
But once this user pulls a bug from repo B he can no longer push back to repo A.
Worse, if the user pulls from A and then B he can no longer contribute back to either repo because A and B might not be interested in the bugs of each other.
And yes, handling this with additional metadata is possible. But I value the ability to transfer bug references across machines with git
itself and namespacing should be familiar to anyone using git
.
from git-bug.
a +1 with my own reasoning
for me, one of the essential qualities of git, is that one is able to fetch from any repo, then look at it locally while still having them separate. then I can use for myself only what I care about and deem worthwhile.
This should be the same for bugs, with maybe the exception of a kind of centralized, public version of the repo, which could be configured to auto-accept all bugs into its own name-space.
It should be the special case, and not the default (or even the only possible) behavior.
I think with this lacking, it will make many devs feel a kind of loss of control they have come to value and expect from normal git workflow with code. One might feel very reluctant to fetch other peoples repos, simply because one does not want to risk getting spammed by others bugs.
from git-bug.
+1. This makes sense.
I currently use git bug as my private issue tracker. Local, only accessible to me—great. But the issues might be of interest to others. Letting them import them under a separate namespace would be nice.
(If that would also help against merge conflicts, that would be great. I have no idea though since I don’t know how git bug is implemented.)
I also don’t want to use SHA-1 for bug ids. git bug probably probably doesn’t support incrementing ids so I’ll probably just do it manually. Then with my namespace the issues could be identified with <namespace>-<integer>
.
from git-bug.
This bot triages untriaged issues and PRs according to the following rules:
- After 90 days of inactivity, the
lifecycle/stale
label is applied - After 30 days of inactivity since
lifecycle/stale
was applied, the issue is closed
To remove the stale status, you can:
- Remove the
lifecycle/stale
label - Comment on this issue
from git-bug.
Related Issues (20)
- git bug push fails with SHA-1 key message HOT 3
- push fails on local origin HOT 1
- Jira Bridge: Project doesn't exist HOT 1
- util/text/validate.go: Safe is not safe HOT 2
- Error: repository not found / Preferred way to deal with multiple git identities HOT 1
- Add ability to add a label when creating a new bug HOT 2
- "Error: rename ... Access is denied" When Creating a Ticket HOT 1
- bridge to https://github.com/charmbracelet/soft-serve HOT 3
- Search for git-bug ID in termui HOT 1
- FTBFS: *GitRepo does not implement ClockedRepo (missing method AllClocks) HOT 4
- CLI usage possibilities were reduced?
- Question : Can issues from a bridge embedded in the git repo ?
- [feature request] support git worktree HOT 1
- 0.8 SSH git push "authorization failed" HOT 3
- git-bug maintenance status HOT 3
- Relocate repository to git-bug/git-bug
- flaky test on windows: //cache/repo_cache_test.go%TestCache
- Convert all pipelines to nested, re-usable workflows
- Use htmx instead of javascript HOT 4
- Bring command documentation up-to-date
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from git-bug.