-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
5 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
635b179
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if you still have time to handle all those PRs, or will they be left stale forever?
635b179
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More likely I’ll close most as many aren’t something I’m interested in adding.
I use the stale status to gauge interest in a PR or issue. Most are narrow focused features or requests not worth the technical debt added to the theme if I were to merge in.
635b179
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand that, but I think they should be acted upon accordingly. Here's my view:
<h1>
through<h6>
#2771And one last special case: #2636 (support for sverrirs/jekyll-paginate-v2) - What about just letting it in for now and let users report further issues? I've been watching this repo for like a year but haven't seen much activity recently
635b179
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May appear as limited activity but I can assure you I read everything from the Jekyll/HTML/CSS questions, to feature requests, to blog update PRs sent to the wrong remote repo, and everything in between.
Lately I’ve been mostly quiet because I don’t really agree with a pull request or feature request enough to comment or close it, so I leave it be.
Hence the stale flag. If there’s enough demand or discussion around it I’m motivated to take a second look and weigh in… which rarely happens.
Usually it’s only the PR author or one other user asking for something that in the long will likely make managing things harder or clashes with my design philosophy for the theme.
At this point I’m more of in maintenance mode with it. Sure there are things I could add or improve on, but that would likely happen with a complete rethink (or fork) of the theme.
635b179
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really appreciate how quickly you close all those wrong PRs and migrate question-type issues to discussions.
Thank you very much for your great project and promptly response. Now I get where you are by "in maintenance mode".
635b179
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would much prefer comments as to why a PR is not being included than have a stale bot just automatically close it without commentary.