Community Theme Vote

[jesterb0206]

I was wondering what it actually takes for a theme to get merged into main? There's pull requests for themes from a year ago or longer that are just sitting there waiting to be merged or shot down. I was thinking the administrator(s) could start a community vote where all pull requests for themes that pass the GitHub Action tests could be voted on and the top 5 or 10 could be merged into main (only a small handful could get approved to avoid bloating). You could give the community say 1 month to vote on themes and then the ones that weren't in the top 5 or 10 could get removed (would help to get rid of a lot of open pull requests). That was just an idea I had, personally I think the pull requests are cluttered and messy right now. You could also have a section in the repository's main README where you show what each of the themes that are up for vote look like and allow each GitHub user that votes to cast votes for 5-10 of their favorite themes. @rickstaa @anuraghazra

[rickstaa]

Hey @jesterb0206. Thanks for your suggestion everything that helps to clean up the PRs is an improvement. 🔥

I implemented the top-issues-dashboard, stale-theme-pr-closer.yaml and improved the preview-theme.yml to do just that some time ago. These changes allowed me to trim the open themes PRs down from more than 140 to about 60.

We currently have no written procedure for merging themes into the main branch. 😅 I currently check the themes once a month and merge the ones that receive the most likes, adhere to the theme guidelines and are not similar to the themes we already have. The last ones that were merged were:

• Add Rosé Pine themes #892
• Transparent theme #1010

The ones that are most close to being merged are:

• Add flag_korea #1264
• Added Date Night theme to index.js #2264

If these receive more than 3 likes, I will take a look. Maybe we can extend the https://github.com/rickstaa/top-issues-action action such that users can specify custom labels for creating sections. 🤔 Doing this would allow us to show the top-voted themes (i.e. themes label), increasing the chance that people will vote for these themes and collaborators will merge them into the main branch. I'm not a fan of manually creating a theme poll every month, but if you can think of another automated solution, don't hesitate to share 👍🏻.

[rickstaa]

@rickstaa While I have you here, I have an off topic question I think you might know the answer too. I forked this repository and I manually update my branch from time to time to keep it up to date with anuraghazra:master. Is there a way I can automate this so I don't have to manually update my branch, I was hoping there was a way you could sync your fork automatically whenever a change was made on the master branch.

This was a often-asked question so I recently added it to the documentation (see https://github.com/anuraghazra/github-readme-stats#keep-your-fork-up-to-date). Feel free to let me know if the solution provided there works.

[rickstaa]

@jesterb0206 I created a feature request that would allow us to add a Top Themes section (see rickstaa/top-issues-action#110). I, however, am a bit limited in time at the moment, so I can not give any promises when I implement this feature. 😅 I added the help-wanted label so other people can work on it.

[rickstaa]

I also created #2270 to track the improvements you suggested. If you have the time and would like to contribute more, you can take on some of the TODOs. 👍🏻

[jesterb0206]

@rickstaa No worries! I'm busy myself right now too so I understand. I appreciate you creating the feature request, hopefully I'll have more time to contribute soon!

[rickstaa]

@jesterb0206 just a heads-up that team voting will be implemented when #2711 is merged.