Refined-github: add an option to show the repos you contribute to

[Thatkookooguy]

I wanted to use this extension, but it hides some things I use on a regular basis and can't seem to find an option to add back

for example, I use the "repos you contribute to" section pretty frequently to quickly navigate to repos I don't own.

is there a way to add that back with the current settings?

thanks

[yakov116]

@Thatkookooguy github created a great tool for that!! The best is you don't even need an extention!

Its called...... The search tool.
Search the repo and you will see that you can add your own custom CSS to add it back

[fregante]

In the options, paste this CSS:

.dashboard-sidebar > .boxed-group[role="navigation"] {
    display: block !important;
}

[fregante]

It turns out it wasn't possible because our CSS was injected before Chrome injects our stylesheet, so our !important was coming after the user's. I short we should avoid !important even more now.

[Thatkookooguy]

@yakov116 I don't know why you need to use that tone of voice. Here, I'll give you a few scenarios:

1. user want to go to a repo they contributed to a week ago, but they don't know the name of (one-time contribution)
2. user want to go to a repo they contribute to alot
3. user want to go to a general repo

now let's look at the different routes for each case

1. you can't even use the search bar to get to that repository
2. you can use both the search bar and the feature I mentioned. With the "repos you contributed to", the repo should be 1 or 2 clicks away. with the search bar, you need to write the name of the repo, which is probably more than 2 clicks away
3. this is the only case of the three which the "repos you contributed to" feature does nothing and the search bar is the better option of the two

Search the repo and you will see that you can add your own custom CSS to add it back

Well... here's @bfred-it comment which might shed some light on this:

It turns out it wasn't possible because our CSS was injected before Chrome injects our stylesheet, so our !important was coming after the user's. I short we should avoid !important even more now.

@yakov116 you can use whatever you want in your workflow. I don't see a reason to make any of these conversations unpleasant.

Thanks everybody for the information! and thanks @bfred-it for the quick fix. I can add it back now :-)