Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UX] make more visible warning for setting repo to private #25085

Closed
6543 opened this issue Jun 5, 2023 · 2 comments
Closed

[UX] make more visible warning for setting repo to private #25085

6543 opened this issue Jun 5, 2023 · 2 comments
Labels
good first issue Likely to be an easy fix issue/duplicate The issue has already been reported. topic/ui Change the appearance of the Gitea UI topic/ui-interaction Change the process how users use Gitea instead of the visual appearance

Comments

@6543
Copy link
Member

6543 commented Jun 5, 2023

Now

image

Originally posted by @42wim in #19904 (comment)

@6543 6543 added good first issue Likely to be an easy fix topic/ui-interaction Change the process how users use Gitea instead of the visual appearance topic/ui Change the appearance of the Gitea UI labels Jun 5, 2023
@6543
Copy link
Member Author

6543 commented Jun 5, 2023

I propose to move this checkbox to the dangeroups part and convert it into a button.
there we can also describe ireversible processes that will happen if clicked

@alystair
Copy link

Dupe of my request #23826

@6543 6543 added the issue/duplicate The issue has already been reported. label Oct 15, 2023
@6543 6543 closed this as completed Oct 15, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Likely to be an easy fix issue/duplicate The issue has already been reported. topic/ui Change the appearance of the Gitea UI topic/ui-interaction Change the process how users use Gitea instead of the visual appearance
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants