You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have a section that shows only content from one repo (with a long name) and I want to save space by not showing the repo name in that section. Similarly in the "My PRs" section I don't want to show the author.
I've tried setting the repo and author columns to hidden: true, but it seems they are already hidden (though setting hidden: false also has no effect? 🤔). It appears all of this info is instead part of the title column, but I don't see a way to customize what is shown there.
Describe the solution you'd like
A way to choose which fields should be included in the "title" column (and perhaps the order too).
The text was updated successfully, but these errors were encountered:
I just discovered that part of the confusion is due to the sparse layout, which is enabled by default. I think it's quite confusing that this makes some of the columns always hidden, it should be at least clearly mentioned in the documentation. But I like the sparse layout and would like to keep using it, just with the ability to customize the title field.
Is your feature request related to a problem? Please describe.
I have a section that shows only content from one repo (with a long name) and I want to save space by not showing the repo name in that section. Similarly in the "My PRs" section I don't want to show the author.
I've tried setting the
repo
andauthor
columns tohidden: true
, but it seems they are already hidden (though settinghidden: false
also has no effect? 🤔). It appears all of this info is instead part of thetitle
column, but I don't see a way to customize what is shown there.Describe the solution you'd like
A way to choose which fields should be included in the "title" column (and perhaps the order too).
The text was updated successfully, but these errors were encountered: