Codeberg/Community

Fork 12

code berg auto drafting realease #2110

New issue

Open

opened 2025-08-28 17:12:31 +02:00 by TheoW03 · 6 comments

TheoW03 commented

2025-08-28 17:12:31 +02:00

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

Gusted commented

2025-08-30 01:32:14 +02:00

Owner

@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?

TheoW03 commented

2025-08-30 23:25:51 +02:00

Author

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.

Gusted commented

2025-09-02 07:29:59 +02:00

Owner

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.

TheoW03 commented

2025-09-02 15:37:48 +02:00

Author

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

Gusted commented

2025-09-04 14:44:28 +02:00

Owner

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

TheoW03 commented

2025-09-07 16:44:58 +02:00

Author

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".

No milestone

No project

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

No description provided.

Rows
Columns