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

Rename actions tabs from Open/Closed to Running/Finished #24553

Closed
wants to merge 3 commits into from

Conversation

js6pak
Copy link
Contributor

@js6pak js6pak commented May 5, 2023

It doesn't make sense for actions to be open or closed so rename them to be running/finished.


Before:
image
With this change:
image

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label May 5, 2023
@pull-request-size pull-request-size bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label May 5, 2023
@lunny
Copy link
Member

lunny commented May 5, 2023

Some tasks are queue, canceled or failed. Is running/finished accurate enough?

@js6pak
Copy link
Contributor Author

js6pak commented May 5, 2023

Cancelled and failed are both finished, just not successfully. For queued I'd say running is good enough.
Ideally there would be no tabs with everything being displayed by default and a filter option like the one github has.
That's beyond this PR though.

@techknowlogick techknowlogick added the topic/ui Change the appearance of the Gitea UI label May 6, 2023
@wolfogre
Copy link
Member

wolfogre commented May 6, 2023

How about:

runs.open_tab = %d Ongoing
runs.closed_tab = %d Finished
  • Keep open_tab and closed_tab unchanged, they are part of the code, not the UI. We should keep them consistent with NumClosedActionRuns.
  • I don't think Running is good enough. It could be confusing with StatusRunning
  • Finished looks good to me.

I'm not a native English speaker, just my opinions from coding.

@yardenshoham
Copy link
Member

For reference, how GitHub classifies these
image

Why do we filter these? Let's just show both open and closed by default

@wxiaoguang
Copy link
Contributor

wxiaoguang commented May 10, 2023

I do not think "Running" is clear either.

I can accept Ongoing / Over

@silverwind
Copy link
Member

silverwind commented May 12, 2023

I guess Active and Completed may be my favorite.

@js6pak
Copy link
Contributor Author

js6pak commented May 13, 2023

@yardenshoham

For reference, how GitHub classifies these image

Why do we filter these? Let's just show both open and closed by default

That's exactly what I said here #24553 (comment)

Seeing as how everyone wants to name these tabs differently should we just skip this PR and go straight into removing the tabs altogether? I really don't see a point in showing only one of the state at the time.

@silverwind
Copy link
Member

silverwind commented May 13, 2023

Yeah I guess actions just don't fit into the 2-state scheme like issues do. I havent' really checked this actions UI yet, but I assume these buttons are non-critical to usage, right?

@wxiaoguang
Copy link
Contributor

I don't want to be too strict, so to clarify my opinion:

For "Open":

  • "Open" is not ideal
  • "Running" doesn't look good to me. Some are queued, not running
  • "Ongoing / Active": look good to me

For "Close":

  • "Close" is not ideal
  • "Completed / Finished" doesn't look good to me, some could be canceled, not completed or finished.
    • But if there is strong preference, I won't block.
  • "Over" is the proper word in my mind: the task is over, god knows what happens to it, just like "Game Over", the player could fail halfway, reach bad ending, or reach happy ending.

@yardenshoham
Copy link
Member

Seeing as how everyone wants to name these tabs differently should we just skip this PR and go straight into removing the tabs altogether? I really don't see a point in showing only one of the state at the time.

I agree #24711

@lunny
Copy link
Member

lunny commented May 14, 2023

replaced by #24711

@lunny lunny closed this May 14, 2023
lunny pushed a commit that referenced this pull request May 14, 2023
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Aug 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. topic/ui Change the appearance of the Gitea UI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants