Fork 40

Support .profile README.md in User profile#1286

New issue

Closed

opened 2023-09-01 12:02:43 +02:00 by Andre601 · 7 comments

Andre601 commented

2023-09-01 12:02:43 +02:00

Made this through your app, so no templates to select from :/

Forgejo (not sure about gitea) added support for having a profile readme by creating a .profile repository with a README.md file in it to display.

It would be cool if Gitnex could support displaying this profile readme when viewing a profile.

> Made this through your app, so no templates to select from :/ Forgejo (not sure about gitea) added support for having a profile readme by creating a `.profile` repository with a README.md file in it to display. It would be cool if Gitnex could support displaying this profile readme when viewing a profile.

👍 1

DrMaxNix commented

2023-09-01 13:43:35 +02:00

Contributor

Can confirm: Gitea also has this feature. It was added in v1.20.0 (https://github.com/go-gitea/gitea/pull/23260).

👍 3

mmarif commented

2023-09-02 08:05:01 +02:00

Owner

@Andre601 this definitely is possible, with:

if the API provide information about the repository somehow in user endpoint OR directly provide the README.md content inside an object

I would love to see an example repository for this in action and whether the API object is necessary to get that info.

@Andre601 this definitely is possible, with: - if the API provide information about the repository somehow in user endpoint OR directly provide the README.md content inside an object I would love to see an example repository for this in action and whether the API object is necessary to get that info.

mmarif added the

🎯 Enhancement

label

2023-09-02 08:05:40 +02:00

Andre601 commented

2023-09-02 23:09:37 +02:00

Author

I'll see that I can propose adding a new API route to Gitea so that it could eventually be merged into Forgejo, if Gitea decides to add it...

Looking at the API docs, there doesn't seem to be any path that would directly provide the profile readme content... At most is there the option to get the files of a repository and then check for the readme, but this would be somewhat unoptimal. I'll see that I can propose adding a new API route to Gitea so that it could eventually be merged into Forgejo, if Gitea decides to add it...

mmarif commented

2023-09-03 07:50:22 +02:00

Owner

That would be great.

mmarif added the

🛰️ API-dependency

label

2023-09-03 07:50:33 +02:00

Andre601 commented

2023-09-03 23:53:52 +02:00

Author

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

Andre601 commented

2023-09-05 11:46:29 +02:00

Author

Gitea contributor suggests to just make a normal request towards {user}/.profile/raw/branch/main/README.md and if it returns 404 treat it like no readme exists.

I'm not too sure about that one tbh. Especially given that the repository may not have main or master defined as their default branches, so it would be guess work here...

Gitea contributor suggests to just make a normal request towards `{user}/.profile/raw/branch/main/README.md` and if it returns 404 treat it like no readme exists. I'm not too sure about that one tbh. Especially given that the repository may not have `main` or `master` defined as their default branches, so it would be guess work here...

mmarif commented

2023-09-19 12:53:17 +02:00

Owner

Gitea contributor suggests to just make a normal request towards {user}/.profile/raw/branch/main/README.md and if it returns 404 treat it like no readme exists.

Maybe he is talking about the web. That path will work on the web version.

To make the this work in GitNex, I can make use of file content API, /repos/{owner}/{repo}/contents/{filepath}. I will check this out in detail soon.

> Gitea contributor suggests to just make a normal request towards {user}/.profile/raw/branch/main/README.md and if it returns 404 treat it like no readme exists. Maybe he is talking about the web. That path will work on the web version. To make the this work in GitNex, I can make use of file content API, `/repos/{owner}/{repo}/contents/{filepath}`. I will check this out in detail soon.

mmarif removed the

🛰️ API-dependency

label

2023-09-19 12:53:49 +02:00

mmarif added this to the 5.2.0 milestone

2023-09-19 19:49:23 +02:00

mmarif self-assigned this

2023-09-19 19:49:30 +02:00

mmarif referenced this issue from a pull request that will close it,

2023-09-19 19:50:09 +02:00

UI enhacements #1300

mmarif referenced this issue from a commit