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

templates: add optional Series ID buttons to the patch list #571

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rossburton
Copy link
Contributor

@rossburton rossburton commented Nov 21, 2023

If the user has turned on display of patch IDs, add another column with the series IDs to the patch list template.

Note that I've not tested this in production because I've not yet setup a local instance...

@rossburton
Copy link
Contributor Author

Now tested!

Had to use a nbsp to stop "Series ID" wrapping and ruining the header alignment.

Screenshot 2023-11-22 at 01 32 52

@rossburton
Copy link
Contributor Author

I'm torn on whether the column should just be called "ID" and let its position clarify what ID it refers to.

@rossburton
Copy link
Contributor Author

Maybe the ID column should just be removed, and the button inline with the patch or series name?

@stephenfin
Copy link
Member

I wonder if, rather than adding another column, we could add the <button> in the existing series column, before the subject? Every bit as clickable but we avoid adding yet more columns to the rather large table.

If the user has turned on display of patch IDs, add clickable series ID
buttons inline with the series name.

Signed-off-by: Ross Burton <[email protected]>
@rossburton
Copy link
Contributor Author

Done.

Screenshot 2024-01-25 at 11 59 03

Would it be sensible to merge the "Patch ID" and "Patch" columns too?

@rossburton
Copy link
Contributor Author

rossburton commented Jan 25, 2024

The good thing about two columns is it forces the alignment...

@rossburton
Copy link
Contributor Author

Polite ping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants