-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Update message of reach_limit_of_creation #21757
Merged
lunny
merged 6 commits into
go-gitea:main
from
wolfogre:bugfix/fix_reach_limit_of_creation
Nov 11, 2022
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
4051080
chore: update reach_limit_of_creation
wolfogre 52bccb1
chore: fix word
wolfogre 3ef3e1c
Merge branch 'main' into bugfix/fix_reach_limit_of_creation
wolfogre 12cd476
Merge branch 'main' into bugfix/fix_reach_limit_of_creation
lafriks 85bacc2
Merge branch 'main' into bugfix/fix_reach_limit_of_creation
techknowlogick 6d09495
Merge branch 'main' into bugfix/fix_reach_limit_of_creation
wolfogre File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But is that the typical situation for this error message?
I think this change will confuse users that actually reached the limit themselves:
The best compromise I can come up with is the following:
Any better ideas?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's the owner not you. When you create a repo under your username, the limitation depends on you. When you create a repo under an org, the limitation depends on the org's limitation. When you create a repo under other user(you are an admin?), the limitation depends on that user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"You or the selected owner" is a little ambiguous, it sounds like you can't create a repo if either you or the owner has reached the limit.
I think the "owner" word may cause a little confusion, but the form is self explanatory, there's still a "owner" selector when the user is creating a repo for himself.