canUserAdminRepo - Support new UI

[dnicolson]

No description provided.

[SunsetTechuila]

Doesn't work if the settings entry is in the dropdown menu

[SunsetTechuila]

Note: before the navbar was rewritten in React, users with just write access to the repo didn't have the Settings tab. They now do, but can only view and edit secrets and variables:

[fregante]

Yeah this PR makes sense on its own but probably the whole function should be deprecated instead. In Refined GitHub we now use th API for this purpose.

@dnicolson can you look at other deprecated functions and do the same for this one? You can keep the changes so far.

[SunsetTechuila]

In Refined GitHub we now use th API for this purpose

canUserAdminRepo is used by clean-repo-tabs, clean-repo-sidebar and show-open-prs-of-forks. All broken right now

[SunsetTechuila]

Maybe we should re-export it with a different name, as it can still be useful. For example, we can use it for refined-github/refined-github#8553 to decide what to fetch: public members or collaborators

[fregante]

Users seeing that errors see it because they aren't members. Adding this check could hide the error, but nothing else. Also I think external collaborators aren't covered (no settings tab)

[SunsetTechuila]

I'm not sure we understood each other. This is what I'm talking about:

const collaborators = pageDetect.canUserAdminRepo() ? fetchCollaborators() : fetchPublicMemebers();

external collaborators aren't covered (no settings tab)

They are

[fregante]

If "fetch public member" works, that's ok I guess. It won't cover all collaborators but probably better than nothing. Please open a new PR to deprecate this and rename it.