sticky-comment-header - Drop feature - #10005
Conversation
|
Test comment |
|
Test 2 |
|
FWIW, I highly value this feature, even with its small shortcomings π ; perhaps leave it be but turn it off by default? So those who really want it can turn it ON at will; FWIW2, PRs are still behind an older layout (non-react), unlike issues, for which the feature (mostly) works as intended; I suspect when GitHub also migrates PRs to react, the bugs on PRs will go away? In any case, thanks for this wonderful extension π ... |
|
Oh no...! Just as it got enabled again π₯² I would also really love for there to be a way to keep this one @fregante if the Refined GitHub team really wants to remove it completely (and you can't just disable by default like @Vangelis66 mentioned), what would you suggest for users who want to use this? I could also imagine another alternative: semi-maintained "recipes" section or something, which are tested to be working at one point in history but have no other maintenance guarantees (so sometimes also have problems). |
|
The cool part of this feature is that it's just CSS so you can copy it from this PR and paste it in the CSS field Refined GitHub provides. Or you can publish it to userstyles dot org and maintain it. There's no point in "recipes" as that would entail some kind of support regardless. As with any rejected features, you're welcome to use this PR to post link to your user styles or post up to date versions of your CSS as changes are needed. |
That already describes all of Refined GitHub π |
As a layman non-coder π , have I got it right that the code to be copied is the one in this deleted file? |
|
Feature dropped, please do not ping me to re-add it in the future. You can use this PR to post updates to the CSS, I'll unsubscribe |
This feature has too many issues, I donβt think it's worth it. Here's the latest one on PRs