Codeberg/Community
54
325
Fork
You've already forked Community
12

code berg auto drafting realease #2110

Open
opened 2025年08月28日 17:12:31 +02:00 by TheoW03 · 6 comments

Comment

a while ago I made a NES ROM disassembler
and I want to release however the release keeps on getting auto drafted and I dont know why?

https://codeberg.org/TheoW03/nesda

here is the repo. I dont think it should violate any of the TOS. I am trying to a both windows build and debian linux build of it

### Comment a while ago I made a NES ROM disassembler and I want to release however the release keeps on getting auto drafted and I dont know why? https://codeberg.org/TheoW03/nesda here is the repo. I dont think it should violate any of the TOS. I am trying to a both windows build and debian linux build of it

@TheoW03 wrote in #2110 (comment):

and I want to release however the release keeps on getting auto drafted and I dont know why?

Could you explain what you mean by the release getting auto drafted?

@TheoW03 wrote in https://codeberg.org/Codeberg/Community/issues/2110#issue-2253133: > and I want to release however the release keeps on getting auto drafted and I dont know why? Could you explain what you mean by the release getting auto drafted?
Author
Copy link

well I post the release, it has the "stable" status.
and usually around 15 minutes later it becomes drafted. like the release gets taken down.

I suspect its a false positive from the auto moderated tools because the same thing actually happens on GitHub.
but I don't get why, as this doesn't violate anything in the TOS. it is not malware, I would never code something for malicous intent, it is a NES ROM disassembler but they are disassemblers some of which are more powerful then my own. on here and on Github.

so there really isn't a reason for it to be taken down like this.

well I post the release, it has the "stable" status. and usually around 15 minutes later it becomes drafted. like the release gets taken down. I suspect its a false positive from the auto moderated tools because the same thing actually happens on GitHub. but I don't get why, as this doesn't violate anything in the TOS. it is not malware, I would never code something for malicous intent, it is a NES ROM disassembler but they are disassemblers some of which are more powerful then my own. on here and on Github. so there really isn't a reason for it to be taken down like this.

There are no moderation tools on Codeberg that have such capability. If you have a timestamp I could check if the release was updated in the server logs, but there's not really any automation code concerning releases that would be able to do this.

There are no moderation tools on Codeberg that have such capability. If you have a timestamp I could check if the release was updated in the server logs, but there's not really any automation code concerning releases that would be able to do this.
Author
Copy link

Timestamp of realease: Aug 28, 2025, 10:58 AM EDT

Timestamp of realease: Aug 28, 2025, 10:58 AM EDT

Hm, not weird according to the logs. Could you document the steps you took to create this release?

Hm, not weird according to the logs. Could you document the steps you took to create this release?
Author
Copy link

What I did was
I had both a .deb file and .exe
Added it in the upload file section

Wrote a short description about it. Gave it a tag I have been connecting it to a branch. prealpha-1.0.0
And published the release.
Around 15 minutes it gets "drafted".

What I did was I had both a .deb file and .exe Added it in the upload file section Wrote a short description about it. Gave it a tag I have been connecting it to a branch. prealpha-1.0.0 And published the release. Around 15 minutes it gets "drafted".
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
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
Codeberg/Community#2110
Reference in a new issue
Codeberg/Community
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?