anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[Idea] organising issues #412

New Issue
Closed
opened 2026-02-16 17:26:39 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 17:26:39 -05:00
Owner
Copy Link
Copy Source

Originally created by @furai on GitHub (Jul 1, 2025).

Originally assigned to: @thdxr on GitHub.

Hey @thdxr @adamdotdevin,

I was wondering what you think about adopting a tagging system for issues in the repo - specifically for things like:

  1. Good First Issues: It would be great to tag issues that are beginner-friendly or suitable for first-time contributors. That way, people can quickly identify opportunities to get involved.
  2. In Progress: It might also help to tag issues when someone is already actively working on them, so others don’t accidentally duplicate effort or step on anyone’s toes.

I'd really like to contribute more, but sometimes I hesitate because I’m unsure if someone is already tackling an issue. A bit of structure around this could help everyone coordinate better.

I know that it's extra time to put into project and you guys want to move quickly but I think it might be worth it.

Cheers,
Furai

Originally created by @furai on GitHub (Jul 1, 2025). Originally assigned to: @thdxr on GitHub. Hey @thdxr @adamdotdevin, I was wondering what you think about adopting a tagging system for issues in the repo - specifically for things like: 1. `Good First Issues`: It would be great to tag issues that are beginner-friendly or suitable for first-time contributors. That way, people can quickly identify opportunities to get involved. 2. `In Progress`: It might also help to tag issues when someone is already actively working on them, so others don’t accidentally duplicate effort or step on anyone’s toes. I'd really like to contribute more, but sometimes I hesitate because I’m unsure if someone is already tackling an issue. A bit of structure around this could help everyone coordinate better. I know that it's extra time to put into project and you guys want to move quickly but I think it might be worth it. Cheers, Furai
yindo closed this issue 2026-02-16 17:26:39 -05:00
yindo commented 2026-02-16 17:26:39 -05:00
Author
Owner
Copy Link
Copy Source

@luuk00101 commented on GitHub (Jul 1, 2025):

Commenting for a bigger chance to have this read :) Sunds like a great idea!

@luuk00101 commented on GitHub (Jul 1, 2025): Commenting for a bigger chance to have this read :) Sunds like a great idea!
yindo commented 2026-02-16 17:26:39 -05:00
Author
Owner
Copy Link
Copy Source

@adamdotdevin commented on GitHub (Jul 1, 2025):

will discuss all things github with dax this morning, including this

@adamdotdevin commented on GitHub (Jul 1, 2025): will discuss all things github with dax this morning, including this
yindo commented 2026-02-16 17:26:39 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 27, 2025):

[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

@rekram1-node commented on GitHub (Dec 27, 2025): [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#412
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?