Add '.profile' repository as its profile repository

[hwhsu1231]

Select Topic Area

Product Feedback

Body

I hope GitHub can add a .profile repository as a user or organization profile repository.

First of all, I know that GitHub already provides user and organization-specific Profile READMEs:

• User: <username>/README.md (see here)
• Organization: .github/profile/README.md (see here)

However, I suggest that GitHub also provide a solution similar to Gitea (see here):

• User: .profile/README.md
• Organization: .profile/README.md

Here are my reasons for this suggestion:

For Organization Profile

Suppose that someone intends to create/maintain a repository in a GitHub organization and use some tools or GitHub Actions to synchronize those repositories to other Git hosting platforms (e.g., Gitea). In that case, the Profile Repository will not be visible on Gitea's personal page when synchronized. This is because:

• The Profile README that works on GitHub is: .github/profile/README.md.
• The Profile README that works on Gitea is: .profile/README.md.

If GitHub and Gitea kept their Profile README designs consistent, the above issue would not occur.

However, since GitHub's organization Profile README considers both "Public" and "Member-Only" modes:

• Public Mode: .github/profile/README.md
• Member-Only Mode: .github-private/profile/README.md

I would instead suggest that Gitea's organization Profile README be changed to:

• Public Mode: .profile/public/README.md
• Member-Only Mode: .profile/private/README.md

For User Profile

Although it seems feasible to request Gitea provide the new profile README location <username>/README.md, it might encounter problems when users have different usernames in GitHub and Gitea. For example:

Suppose that a user registered his username as @naruto in GitHub, but registered his username as @naruto01 in Gitea (because @naruto is already registered by someone else in Gitea). In that case, if he mirrored his Profile Repository from GitHub to Gitea, then the Profile Repository will not be visible on Gitea's personal page when synchronized. This is because:

• The Profile README that works on GitHub is: naruto/README.md.
• The Profile README that works on Gitea will be: naruto01/README.md.

And if both GitHub and Gitea adopt this form of profile README location .profile/README.md, then the above issue would not occur.

Conclusion

In short, what I want to emphasize is: I hope that we can establish a common standard for Profile README across all Git hosting platforms.