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

UI: Rename maintaince "Push" button based on project/component settings #9176

Closed
2 tasks done
buhtz opened this issue Apr 28, 2023 · 8 comments
Closed
2 tasks done

UI: Rename maintaince "Push" button based on project/component settings #9176

buhtz opened this issue Apr 28, 2023 · 8 comments
Assignees
Labels
enhancement Adding or requesting a new feature. ux Issues related to user experience.
Milestone

Comments

@buhtz
Copy link

buhtz commented Apr 28, 2023

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

  • I've read and searched the documentation.
  • I've searched for similar issues in this repository.

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

image

Exception traceback

No response

How do you run Weblate?

Other

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

@buhtz
Copy link
Author

buhtz commented Apr 28, 2023

#8535

@nijel
Copy link
Member

nijel commented Apr 28, 2023

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).

@nijel nijel self-assigned this Apr 28, 2023
@nijel nijel added enhancement Adding or requesting a new feature. ux Issues related to user experience. labels Apr 28, 2023
@nijel nijel added this to the 4.18 milestone Apr 28, 2023
@buhtz
Copy link
Author

buhtz commented Apr 28, 2023

Well, it does both push (to a fork/branch) and create a pull/merge request in that case.

From a UI designers perspective it doesn't matter what "it does" but what the "users understand what happens".
On a shell I can do git push. That is a "Push".
On a code hoster I can create a PullRequest (or MergeRequest on GitLab). That is a "PullRequest".
Two totally different things from a users perspective.

A good UI should reflect the users perspective and/or guide him gently around it there is a need to.

@nijel
Copy link
Member

nijel commented Apr 28, 2023

I'm not saying that the current look is good, but that it only describes part of the operation :-).

nijel added a commit that referenced this issue Apr 28, 2023
That is not really useful at it always contains 0.

See #9176
@nijel nijel closed this as completed in 20f06c4 Apr 28, 2023
@github-actions
Copy link

Thank you for your report; the issue you have reported has just been fixed.

  • In case you see a problem with the fix, please comment on this issue.
  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

@nijel
Copy link
Member

nijel commented Apr 28, 2023

Revamped repository maintenance:

image

@buhtz
Copy link
Author

buhtz commented Apr 28, 2023

What changed? I still see the "Push" button here.

@nijel
Copy link
Member

nijel commented Apr 28, 2023

There is a service specific description next to it, for Gitea it is defined here:

push_label = gettext_lazy("This will push changes and create Gitea pull request.")

The button is still called "Push" as I don't see a better short naming here. Suggestions are welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adding or requesting a new feature. ux Issues related to user experience.
Projects
None yet
Development

No branches or pull requests

2 participants