-
-
Notifications
You must be signed in to change notification settings - Fork 959
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
UI: Rename maintaince "Push" button based on project/component settings #9176
Comments
Well, it does both push (to a fork/branch) and create a pull/merge request in that case. But it makes sense to have a more verbose text here (I've already rewritten some of that page in 9c8dfd0). |
From a UI designers perspective it doesn't matter what "it does" but what the "users understand what happens". A good UI should reflect the users perspective and/or guide him gently around it there is a need to. |
I'm not saying that the current look is good, but that it only describes part of the operation :-). |
That is not really useful at it always contains 0. See #9176
Thank you for your report; the issue you have reported has just been fixed.
|
What changed? I still see the "Push" button here. |
There is a service specific description next to it, for Gitea it is defined here: Line 1117 in 20f06c4
The button is still called "Push" as I don't see a better short naming here. Suggestions are welcome. |
Describe the issue
In the maintaince section there is a button labeld "Push". This doesn't make sense when the component is setup to do PullRequests to the upstream repo.
I already tried
Steps to reproduce the behavior
Setup "PullRequest" and look into maintaince section.
Expected behavior
Name the button "Push" when the component is setup with push behavior.
Name it "Create PullRequest" when PR behavior is setup.
Or just name it "Sync with upstream repo" in all cases.
Screenshots
Exception traceback
No response
How do you run Weblate?
Other
Weblate versions
No response
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: