github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-16 04:42:51 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Move useless comments from source to Issues #30

New Issue
Closed
opened 2025-11-02 03:05:00 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 03:05:00 -06:00
Owner
Copy Link

Originally created by @bkcsoft on GitHub (Nov 4, 2016).

Running make fixme todo will print a nice list of TODO/FIXME-comments from source files. These should be moved to proper issues so that they can be 1) tracked and 2) people actually know about them 😆

There are more instances of these comments throughout the code, and those should be moved as well.

Thoughts?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38952940-move-useless-comments-from-source-to-issues?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).
Originally created by @bkcsoft on GitHub (Nov 4, 2016). Running `make fixme todo` will print a nice list of `TODO/FIXME`-comments from source files. These should be moved to proper issues so that they can be 1) tracked and 2) people actually know about them :laughing: There are more instances of these comments throughout the code, and those should be moved as well. Thoughts? <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38952940-move-useless-comments-from-source-to-issues?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>
GiteaMirror added the type/proposal label 2025-11-02 03:05:00 -06:00
GiteaMirror commented 2025-11-02 03:05:00 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Nov 4, 2016):

The existence of fixme and todo rules clearly makes those code comments NOT useless :)
If the issues creation/deletion can be automated then go for it, otherwise there's a risk of code and issues going out of sync.

I'd love for issues to be closer to code ..

@strk commented on GitHub (Nov 4, 2016): The existence of `fixme` and `todo` rules clearly makes those code comments NOT useless :) If the issues creation/deletion can be automated then go for it, otherwise there's a risk of code and issues going out of sync. I'd love for issues to be closer to code ..
GiteaMirror commented 2025-11-02 03:05:01 -06:00
Author
Owner
Copy Link

@mrsdizzie commented on GitHub (Sep 7, 2020):

Closing since we aren't going to remove these code comments

As an alternative to creating issues for each one there is this service which lists all TODO/fixme type comments for reference:

https://www.tickgit.com/browse?repo=github.com/go-gitea/gitea

And also provides a link to open an issue from any particular comment

@mrsdizzie commented on GitHub (Sep 7, 2020): Closing since we aren't going to remove these code comments As an alternative to creating issues for each one there is this service which lists all TODO/fixme type comments for reference: https://www.tickgit.com/browse?repo=github.com/go-gitea/gitea And also provides a link to open an issue from any particular comment
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 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#30
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?