Deleting a branch is permanent. It CANNOT be undone. Continue?
Labels
No Label
Milestone
No Milestone
Assignees
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
This issue currently doesn't have any dependencies.
Loading…
There is no content yet.
Delete Branch '%!s(MISSING)'
(I thought there was another issue asking something like "What other major services could Codeberg provide?", can't find it though)
How about Gists?
Background:
As (still) a Golang noob I am trying to run Go-Fed apcore activitypub example server. An involved process and I'm keeping notes. Notes are long, mixed of noob misunderstanding, project feedback, and stuff to improve later on with multiple issues + PR's.
There's no good place for the notes. Not suitable as an issue, cannot dump on Matrix, and not suitable for SocialHub forum. So...
How nice if I could have Codeberg gist instead, and refer to it from a GH issue in the project's tracker :)
@momar built https://github.com/qbin-io/qbin
Agree. Yes, there are thousands of pastebin services out there, but using a nice one for Codeberg would be pretty cool.
Is there even one developed on Codeberg?
The best thing would be to integrate it into Codeberg, like having a button in the official UI or being able to sign in into the bin service to manage pastes or assign them to users / projects etc ...
so you just have to look for a pastebin witch has oauth2 login, create a subdomain and that mainly should it be
https://github.com/awesome-selfhosted/awesome-selfhosted#pastebins
EDIT: I could not find a good fit in the first place :/ so it looks we have to programm it ...
Upstream issue: https://github.com/go-gitea/gitea/issues/693
The way that GitHub gists service works, is that it is an oauth application that uses the Github user account to login with.
One benefit of Gist is that each gist is a repo that can be cloned, etc..
A quick way to get started would be to have a "login w/ codeberg" to get oauth2 credentials, and then use the API to create repos & read/write to them.
As for upstream in Gitea, things that would need to be considered are githooks to prevent creating gists w/ folders (to match github gist behaviour), a different way to display them than standard repos (where standard repos only show content of readme, where gists would need to show all files), and also how to display them (likely a different tab from user's profile) so a sql where clause would be needed so they would be excluded from the main repo listing. And maybe comments on gists too (possible forking too)?
Would these work somewhat similar to the wiki repos?
Indeed.