github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-10 05:32:52 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

project.issues.git #1884

New Issue
Closed
opened 2025-11-02 04:16:26 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 04:16:26 -06:00
Owner
Copy Link

Originally created by @a7hybnj2 on GitHub (Jun 6, 2018).

Provide functionality similar to project.wiki.git for issues as well.
Make project.issues.git a stand alone repo to easy pull and manage issues.

Originally created by @a7hybnj2 on GitHub (Jun 6, 2018). Provide functionality similar to project.wiki.git for issues as well. Make project.issues.git a stand alone repo to easy pull and manage issues.
GiteaMirror added the type/proposalreviewed/wontfix labels 2025-11-02 04:16:26 -06:00
GiteaMirror commented 2025-11-02 04:16:27 -06:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 6, 2018):

With each issue in a seperate folder with markdown files for comments and such?

@kolaente commented on GitHub (Jun 6, 2018): With each issue in a seperate folder with markdown files for comments and such?
GiteaMirror commented 2025-11-02 04:16:27 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 24, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 24, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:16:27 -06:00
Author
Owner
Copy Link

@a7hybnj2 commented on GitHub (Jan 24, 2019):

Popular request: Export issues to Excel and/or generate PDF #4808

I like the idea of making the issues a git repo because then you could pull and manage them just like wiki or main repo. Better than exporting to PDF like #4808

@a7hybnj2 commented on GitHub (Jan 24, 2019): Popular request: Export issues to Excel and/or generate PDF #4808 I like the idea of making the issues a git repo because then you could pull and manage them just like wiki or main repo. Better than exporting to PDF like #4808
GiteaMirror commented 2025-11-02 04:16:27 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 26, 2019):

@a7hybnj2 It's difficult to do that since all issues are stored in database.

@lunny commented on GitHub (Mar 26, 2019): @a7hybnj2 It's difficult to do that since all issues are stored in database.
GiteaMirror commented 2025-11-02 04:16:27 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Mar 26, 2019):

I'm setting this as won't fix because of current architecture I don't see how this could be implemented via git protocol

@lafriks commented on GitHub (Mar 26, 2019): I'm setting this as won't fix because of current architecture I don't see how this could be implemented via git protocol
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label reviewed/wontfix type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1884
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?