lix-project/meta
18
1
Issues 16 Projects Activity

Archive the issue mirror and replace it with an issue import bot maybe? #32

New issue
Open
opened 2024-05-10 06:25:11 +00:00 by jade · 0 comments
jade commented 2024-05-10 06:25:11 +00:00
Owner
Copy link

We would like to be able to import nixos/nix issues, but we don't need to keep metadata outside the Lix repo on them anymore, since we don't care about tracking our status of whether we have specific nixos/nix issues anymore: if it's a bug in Lix, it's a bug in Lix, since we have sufficiently diverged to not have most of their bugs anymore (given that we lack libgit2 and lazy trees).

Alternatively we can just can the idea of importing nixos/nix issues, but there is something nice about being able to copy an issue without doing any real thinking. I'm just not 100% sure how the workflow should work: maybe it should be a special issue template where you put in the issue number and it will hit a webhook and trigger the import or something. Or maybe we just have a script. But shrug, this all seems like a lot of work for something we don't think will be super common.

Deciding to can the whole thing would fix: lix-project/web-services#60

We would like to be able to import nixos/nix issues, but we don't need to keep metadata outside the Lix repo on them anymore, since we don't care about tracking our status of whether we have specific nixos/nix issues anymore: if it's a bug in Lix, it's a bug in Lix, since we have sufficiently diverged to not have most of their bugs anymore (given that we lack libgit2 and lazy trees). Alternatively we can just can the idea of importing nixos/nix issues, but there is something nice about being able to copy an issue without doing any real thinking. I'm just not 100% sure how the workflow should work: maybe it should be a special issue template where you put in the issue number and it will hit a webhook and trigger the import or something. Or maybe we just have a script. But shrug, this all seems like a lot of work for something we don't think will be super common. Deciding to can the whole thing would fix: https://git.lix.systems/lix-project/web-services/issues/60
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels   
A-infra

   
A-matrix
No labels
A-infra
A-matrix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/meta#32
No description provided.
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?