Gist like repo type #7681

@crueber commented on GitHub (Aug 11, 2021):

* show a tab with commits/revisions not with as list of commits but with a list of diff-views

I feel like this isn't even really necessary, myself. Certainly a nicety though.

@crueber commented on GitHub (Aug 11, 2021): > * show a tab with commits/revisions not with as list of commits but with a list of diff-views I feel like this isn't even really necessary, myself. Certainly a nicety though.

GiteaMirror commented

@lunny commented on GitHub (Aug 12, 2021):

So that we also need a new column in repository table named uuid.

@lunny commented on GitHub (Aug 12, 2021): So that we also need a new column in repository table named `uuid`.

GiteaMirror commented

@techknowlogick commented on GitHub (Aug 12, 2021):

So that we also need a new column in repository table named uuid.

We won't, as we can use repo_name with and populate it with uuid

@techknowlogick commented on GitHub (Aug 12, 2021): > So that we also need a new column in repository table named uuid. We won't, as we can use repo_name with and populate it with uuid

GiteaMirror commented

@OhYee commented on GitHub (Aug 31, 2021):

URL: <base-url>/<user_or_organization>/gists/<uuid> (gists must be a blacklisted repo name)

Is it possible to implement anonymous code paste?
Like https://paste.ubuntu.com/

It seems that in the current design, an account must be logged in

@OhYee commented on GitHub (Aug 31, 2021): > URL: `<base-url>/<user_or_organization>/gists/<uuid>` (`gists` must be a blacklisted repo name) Is it possible to implement anonymous code paste? Like https://paste.ubuntu.com/ It seems that in the current design, an account must be logged in

GiteaMirror commented

@crapStone commented on GitHub (Sep 6, 2021):

Gists are a way to share information with one or a few files.

You want a pastebin-like service and there is another issue where this is discussed (#693).

@crapStone commented on GitHub (Sep 6, 2021): Gists are a way to share information with one or a few files. You want a pastebin-like service and there is another issue where this is discussed (#693).

GiteaMirror commented

@lunny commented on GitHub (Sep 7, 2021):

Just close this and please discuss further in #693

@lunny commented on GitHub (Sep 7, 2021): Just close this and please discuss further in #693

GiteaMirror commented

@crapStone commented on GitHub (Sep 8, 2021):

This is not a duplicate of #693. I want to have gists and not an anonymous text sharing service.

@crapStone commented on GitHub (Sep 8, 2021): This is not a duplicate of #693. I want to have gists and not an anonymous text sharing service.

GiteaMirror commented

@crapStone commented on GitHub (Sep 8, 2021):

Btw: the discussion in #693 is closed

@crapStone commented on GitHub (Sep 8, 2021): Btw: the discussion in #693 is closed

GiteaMirror commented

@6543 commented on GitHub (Sep 10, 2021):

@lunny did close old issue -> see reason - this proposal here is a better aproach and wont add much extra code etc ...

@6543 commented on GitHub (Sep 10, 2021): @lunny did close old issue -> see reason - this proposal here is a better aproach and wont add much extra code etc ...

GiteaMirror commented

https://gitlab.com/explore/snippets
https://gist.github.com/discover

@psjbeisler commented on GitHub (Feb 1, 2022):

Gists / Snippets always had a social aspect to them and with Federation coming up, the thought of a (possibly Federated) Gitea snippet feed is cool.

@psjbeisler commented on GitHub (Feb 1, 2022): Gists / Snippets always had a social aspect to them and with Federation coming up, the thought of a (possibly Federated) Gitea snippet feed is cool. https://gitlab.com/explore/snippets https://gist.github.com/discover

GiteaMirror commented

@bryanpedini commented on GitHub (Feb 5, 2022):

We won't, as we can use repo_name with and populate it with uuid

⁉️ ⁉️ ⁉️
repo_name is "gists"...

also, my 2c, I think GH uses the commit ID as URL, which IMO is actually easier to handle than "actual routing"

PS: please (if possible, dunno, not a Gitea coder) use .gists or .somethingelse as reserved repo name, I mean, something that nobody would possibly think to use, with a dot before or an underscore or something, not something "plaintext"...

@bryanpedini commented on GitHub (Feb 5, 2022): > We won't, as we can use repo_name with and populate it with uuid ⁉️ ⁉️ ⁉️ `repo_name` is "gists"... also, my 2c, I think GH uses the commit ID as URL, which IMO is actually easier to handle than "actual routing" PS: please (if possible, dunno, not a Gitea coder) use `.gists` or `.somethingelse` as reserved repo name, I mean, something that nobody would possibly think to use, with a dot before or an underscore or something, not something "plaintext"...

GiteaMirror commented

@techknowlogick commented on GitHub (Feb 5, 2022):

@bryanpedini Github uses a fresh repo for each gist, as otherwise when cloning people could discover secret gists, as well if using the commit ID the gist would change location on each change

@techknowlogick commented on GitHub (Feb 5, 2022): @bryanpedini Github uses a fresh repo for each gist, as otherwise when cloning people could discover secret gists, as well if using the commit ID the gist would change location on each change

GiteaMirror commented

@realaravinth commented on GitHub (Feb 18, 2022):

Hello,

I'm working on a gist program which will have features very similar GitHub Gists but with subtle differences:

Directories are permitted: multi-file gists are already permitted in all implementations that I surveyed, directories allow for better organization, which is nice.
Federation via Activity Pub: I want to support federated comments but to do that, I'll also have to support federated gists(what will users comment on? :D), therefore gists and comments will be federated(federated forking, star/favorite and comments)

Currently, it has a standalone authentication/user management mechanism(i.e people can signup using email IDs), but OAuth integration with Gitea is planned. The full feature list is available on the repository's README.

I would appreciate any inputs you might have :)

@realaravinth commented on GitHub (Feb 18, 2022): Hello, [I'm working on a gist program](https://github.com/realaravinth/gists) which will have features very similar GitHub Gists but with subtle differences: - Directories are permitted: [multi-file gists are already permitted in all implementations that I surveyed](https://github.com/realaravinth/gists/blob/master/docs/ecosystem.md), directories allow for better organization, which is nice. - Federation via Activity Pub: I want to support federated comments but to do that, I'll also have to support federated gists(what will users comment on? :D), therefore gists and comments will be federated(federated forking, star/favorite and comments) Currently, it has a standalone authentication/user management mechanism(i.e people can signup using email IDs), but OAuth integration with Gitea is planned. The full [feature list is available on the repository's README](https://github.com/realaravinth/gists#features). I would appreciate any inputs you might have :)

GiteaMirror commented

@ptman commented on GitHub (Feb 18, 2022):

@realaravinth are the features listed already implemented or is that a feature-todo in the readme?

@ptman commented on GitHub (Feb 18, 2022): @realaravinth are the features listed already implemented or is that a feature-todo in the readme?

GiteaMirror commented

@realaravinth commented on GitHub (Feb 18, 2022):

@ptman it's a todo list :)

The project is less than a week old but I hope to get posting gists and commenting on it from the web UI working by the end of next week.

The following things are implemented so far:

Authentication
Account management(credential updates, account deletion, etc.)
Adding gists and reading gists

But all of the above features are implemented using REST API only. Web UI is in progress.

@realaravinth commented on GitHub (Feb 18, 2022): @ptman it's a todo list :) The project is less than a week old but I hope to get posting gists and commenting on it from the web UI working by the end of next week. The following things are implemented so far: - Authentication - Account management(credential updates, account deletion, etc.) - Adding gists and reading gists But all of the above features are implemented using REST API only. Web UI is in progress.

GiteaMirror commented

@Kcalb35 commented on GitHub (Apr 5, 2022):

Are there any news or progress?

@Kcalb35 commented on GitHub (Apr 5, 2022): Are there any news or progress?

GiteaMirror commented

@RokkuCode commented on GitHub (May 16, 2022):

@realaravinth @ptman would you mind to discuss this outside of this issue. i am not interested in a third party tool but i want to see gists in gitea. thanks.

@RokkuCode commented on GitHub (May 16, 2022): @realaravinth @ptman would you mind to discuss this outside of this issue. i am not interested in a third party tool but i want to see gists in gitea. thanks.

GiteaMirror commented

@bryanpedini commented on GitHub (Sep 26, 2022):

I check this issue every day

Cool, good for you, you seem to have time to waste here instead of hands-on the code then...

I want Gist in Gitea

"want"? do it yourself then :)
"desire"? you can pay somebody to do it for you
"would like"? you can wait like everybody else since here nobody's at your service

Keep the drama for yourself, I'm not capable of programming at this level of Go, hence I'm not here complaining about "when this will be avaaaailableee sob sob sob"...

Thanks.

@bryanpedini commented on GitHub (Sep 26, 2022): > I check this issue every day Cool, good for you, you seem to have time to waste here instead of hands-on the code then... > I want Gist in Gitea "want"? do it yourself then :) "desire"? you can pay somebody to do it for you "would like"? you can wait like everybody else since here nobody's at your service Keep the drama for yourself, I'm not capable of programming at this level of Go, hence I'm not here complaining about "when this will be avaaaailableee sob sob sob"... Thanks.

GiteaMirror commented

https://app.bountysource.com/issues/100356521-gist-like-repo-type

@squirrelroad commented on GitHub (Nov 25, 2022):

Hello, I put up an bounty for this request. Hopefully, more users can chip in and incentivize the devs to prioritize this :)

(PS: I understand gitea is meant to be as lean as possible, this feature may be out of scope, however does gitea supports plugins so that new features can be added?)

@squirrelroad commented on GitHub (Nov 25, 2022): Hello, I put up an bounty for this request. Hopefully, more users can chip in and incentivize the devs to prioritize this :) https://app.bountysource.com/issues/100356521-gist-like-repo-type (PS: I understand gitea is meant to be as lean as possible, this feature may be out of scope, however does gitea supports plugins so that new features can be added?)

GiteaMirror commented

@tahaghafuri commented on GitHub (Nov 25, 2022):

UP+

@tahaghafuri commented on GitHub (Nov 25, 2022): UP+

GiteaMirror commented

https://github.com/go-gitea/gitea/issues/22039

@tahaghafuri commented on GitHub (Dec 7, 2022):

@tahaghafuri commented on GitHub (Dec 7, 2022): https://github.com/go-gitea/gitea/issues/22039

GiteaMirror commented

@techknowlogick commented on GitHub (Dec 7, 2022):

@tahaghafuri thank you for your enthusiasm for this ticket. Please keep discussion of the ticket limited to this issue, no need to open multiple other tickets.

@techknowlogick commented on GitHub (Dec 7, 2022): @tahaghafuri thank you for your enthusiasm for this ticket. Please keep discussion of the ticket limited to this issue, no need to open multiple other tickets.

GiteaMirror commented

2025-11-02 07:33:25 -06:00

@splashsky commented on GitHub (Apr 6, 2023):

How is this looking at the moment?

@splashsky commented on GitHub (Apr 6, 2023): How is this looking at the moment?

GiteaMirror commented

@ptman commented on GitHub (Apr 12, 2023):

https://github.com/thomiceli/opengist

@ptman commented on GitHub (Apr 12, 2023): https://github.com/thomiceli/opengist

GiteaMirror commented

2025-11-02 07:33:25 -06:00

@crueber commented on GitHub (Apr 13, 2023):

https://github.com/thomiceli/opengist

I want to applaud you for just going and getting it done. I'll definitely be using yours for the time being. I would prefer that it was tied in to the Gitea auth system, but for my current needs, that's great. Thanks for the advert here.

@crueber commented on GitHub (Apr 13, 2023): > https://github.com/thomiceli/opengist I want to applaud you for just going and getting it done. I'll definitely be using yours for the time being. I would prefer that it was tied in to the Gitea auth system, but for my current needs, that's great. Thanks for the advert here.

GiteaMirror commented

@ptman commented on GitHub (Apr 20, 2023):

Not mine but @thomiceli . I would also prefer that it was integrated to gitea instead of separate and duplicating lots of functionality. But it can auth via gitea.

@ptman commented on GitHub (Apr 20, 2023): Not mine but @thomiceli . I would also prefer that it was integrated to gitea instead of separate and duplicating lots of functionality. But it can auth via gitea.

GiteaMirror commented

@realies commented on GitHub (Jul 11, 2023):

A few years ago, I wondered if this was being worked on. I am surprised not to see it in Gitea today.

@realies commented on GitHub (Jul 11, 2023): A few years ago, I wondered if this was being worked on. I am surprised not to see it in Gitea today.

GiteaMirror commented

@Mai-Lapyst commented on GitHub (Jul 12, 2023):

A few years ago, I wondered if this was being worked on. I am surprised not to see it in Gitea today.

No, currently no-one is working on this. And tbh please on all you out there: if you want it so badly for years then start working on it yourself instead of pinging this issue every few months.

@Mai-Lapyst commented on GitHub (Jul 12, 2023): > A few years ago, I wondered if this was being worked on. I am surprised not to see it in Gitea today. No, currently no-one is working on this. And tbh please on all you out there: if you want it so badly for *years* then start working on it yourself instead of pinging this issue every few months.

GiteaMirror commented

@crapStone commented on GitHub (Jan 15, 2024):

https://github.com/thomiceli/opengist

This works perfectly and can be registered as OAuth application in Gitea

@crapStone commented on GitHub (Jan 15, 2024): > https://github.com/thomiceli/opengist This works perfectly and can be registered as OAuth application in Gitea

GiteaMirror commented

@Mai-Lapyst commented on GitHub (Jan 15, 2024):

@crapStone

https://github.com/thomiceli/opengist

This works perfectly and can be registered as OAuth application in Gitea

... once more: please only bump this issue if this feature is being added into gitea. All people following this issue are well aware that there are 3rd party tools you can plug into it and it kinda works. But we want this as first-party solution inside gitea. Thanks.

@Mai-Lapyst commented on GitHub (Jan 15, 2024): @crapStone > > https://github.com/thomiceli/opengist > > This works perfectly and can be registered as OAuth application in Gitea ... once more: please only bump this issue if this feature is being added **into gitea**. All people following this issue are well aware that there are 3rd party tools you can plug into it and it *kinda* works. But we want this as first-party solution **inside gitea**. Thanks.

GiteaMirror commented

@6543 commented on GitHub (Jan 15, 2024):

I emphasize not bloating gitea ... so this is a perfect solution in my eyes.

why add more maintenance burden if you gain nothing beside copy paste something who is already easy to host too ?!?

@6543 commented on GitHub (Jan 15, 2024): I emphasize not bloating gitea ... so this is a perfect solution in my eyes. why add more maintenance burden if you gain nothing beside copy paste something who is already **easy** to host too ?!?

GiteaMirror commented

@Mai-Lapyst commented on GitHub (Jan 15, 2024):

I emphasize not bloating gitea ... so this is a perfect solution in my eyes.

why add more maintenance burden if you gain nothing beside copy paste something who is already easy to host too ?!?

Easy: From a administration side, I dont want to run, maintain, configure, test multiple services if I dont have to. Espc checking for updates, diffing config settings, doing the actual update + maybe managing downtime with users.

Also from a user point of view, I hate it to logging into multiple sites, remember multiple urls. It also is a problem when you want a consistent style between the gitea and the gist service; espc when it comes to editing experience. This is better handled inside gitea itself imo.

And if we argue of maintenance burden, we also could argue gitea should not have a ci tool as well, as it might not be needed by everyone, yet it is added since it is a sensefull and good addition. Same applies to gists imho.

@Mai-Lapyst commented on GitHub (Jan 15, 2024): > I emphasize not bloating gitea ... so this is a perfect solution in my eyes. > > why add more maintenance burden if you gain nothing beside copy paste something who is already **easy** to host too ?!? Easy: From a administration side, I dont want to run, maintain, configure, test multiple services if I dont have to. Espc checking for updates, diffing config settings, doing the actual update + maybe managing downtime with users. Also from a user point of view, I hate it to logging into multiple sites, remember multiple urls. It also is a problem when you want a consistent style between the gitea and the gist service; espc when it comes to editing experience. This is better handled inside gitea itself imo. And if we argue of maintenance burden, we also could argue gitea should not have a ci tool as well, as it might not be needed by everyone, yet it is added since it is a sensefull and good addition. Same applies to gists imho.

GiteaMirror commented