[GH-ISSUE #345] Think about merging policy of this repository #4199

New Issue

GiteaMirror · 2026-05-01T21:17:19-05:00

GiteaMirror commented

2026-05-01 21:17:19 -05:00

Originally created by @peaceiris on GitHub (Mar 6, 2020).
Original GitHub issue: https://github.com/sdras/awesome-actions/issues/345

See #321.

We can define our policy of this repository before adding fresh actions. This repository is Awesome list, not new arrival list. And, a matter of main concern is maintainability. The more new actions, the more burden for reviewing by maintainers of this repository. I started to worry about this at #321.

How many stars?
How long time has passed since an action repository started?
Vote for a pull request?

Examples

The submitted project should be more than 30 days old and the repo should have at least 30 stars.
awesome-nodejs/contributing.md

I will keep some pull requests open if I'm not sure whether those libraries are awesome, you could vote for them by adding 👍 to them. Pull requests will be merged when their votes reach 20.
vinta/awesome-python

Originally created by @peaceiris on GitHub (Mar 6, 2020). Original GitHub issue: https://github.com/sdras/awesome-actions/issues/345 See #321. We can define our policy of this repository before adding fresh actions. This repository is *Awesome list*, not *new arrival list*. And, *a matter of main concern is maintainability*. The more new actions, the more burden for reviewing by maintainers of this repository. I started to worry about this at #321. - How many stars? - How long time has passed since an action repository started? - Vote for a pull request? ## Examples > The submitted project should be more than 30 days old and the repo should have at least 30 stars. > [awesome-nodejs/contributing.md](https://github.com/sindresorhus/awesome-nodejs/blob/c975c07f6c738e4342f35bc51808ff11a976cea0/contributing.md) > I will keep some pull requests open if I'm not sure whether those libraries are awesome, you could vote for them by adding 👍 to them. Pull requests will be merged when their votes reach 20. > [vinta/awesome-python](https://github.com/vinta/awesome-python/tree/eb46fb3ed4f4688b9d06e4920f5ab53f94d4fd43)

GiteaMirror closed this issue

2026-05-01 21:17:19 -05:00

GiteaMirror commented

2026-05-01 21:17:20 -05:00

@jessicalostinspace commented on GitHub (Mar 6, 2020):

One of the most awesome things about this list is people can contribute to it to show others what is capable with actions in a succinct way, and allows them to get their work out in the public(so that people can star those repositories).

Actions are relatively new and still evolving, and aren’t necessarily as established as nodejs and python. It looks like a quick pass of links here with less than 30 stars would cut this repository down to half or less at this time. If the goal is to get those most starred repositories here, let’s write a scraper that sorts all GitHub Actions to replace this list.

Another alternative is to write an action to scan all the repos in this list to check for the requirements that are set in the new policy :)

@jessicalostinspace commented on GitHub (Mar 6, 2020): One of the most awesome things about this list is people can contribute to it to show others what is capable with actions in a succinct way, and allows them to get their work out in the public(so that people can star those repositories). Actions are relatively new and still evolving, and aren’t necessarily as established as nodejs and python. It looks like a quick pass of links here with less than 30 stars would cut this repository down to half or less at this time. If the goal is to get those most starred repositories here, let’s write a scraper that sorts all GitHub Actions to replace this list. Another alternative is to write an action to scan all the repos in this list to check for the requirements that are set in the new policy :)

GiteaMirror commented

2026-05-01 21:17:21 -05:00

@peaceiris commented on GitHub (Mar 6, 2020):

One of the most awesome things about this list is people can contribute to it to show others what is capable with actions in a succinct way, and allows them to get their work out in the public(so that people can star those repositories).

GitHub Actions Marketplace already plays the role. This repository does not need to repeat the work of the official marketplace.

Actions are relatively new and still evolving, and aren’t necessarily as established as nodejs and python. It looks like a quick pass of links here with less than 30 stars would cut this repository down to half or less at this time. If the goal is to get those most starred repositories here, let’s write a scraper that sorts all GitHub Actions to replace this list.

Another alternative is to write an action to scan all the repos in this list to check for the requirements that are set in the new policy :)

Yes. This kind of action or tool is useful for all awesome lists, not only for this repository. Currently, I do not know actions or tools like that.

@peaceiris commented on GitHub (Mar 6, 2020): > One of the most awesome things about this list is people can contribute to it to show others what is capable with actions in a succinct way, and allows them to get their work out in the public(so that people can star those repositories). [GitHub Actions Marketplace](https://github.com/marketplace?type=actions) already plays the role. This repository does not need to repeat the work of the official marketplace. > Actions are relatively new and still evolving, and aren’t necessarily as established as nodejs and python. It looks like a quick pass of links here with less than 30 stars would cut this repository down to half or less at this time. If the goal is to get those most starred repositories here, let’s write a scraper that sorts all GitHub Actions to replace this list. > > Another alternative is to write an action to scan all the repos in this list to check for the requirements that are set in the new policy :) Yes. This kind of action or tool is useful for all awesome lists, not only for this repository. Currently, I do not know actions or tools like that.

GiteaMirror commented

2026-05-01 21:17:21 -05:00

@gortcodes commented on GitHub (Mar 6, 2020):

I'd recommend regular pruning over gating additions. Many of the actions in the list with a substantial number of stars did not start receiving stars until they were added to the list.

@peaceiris as an example, here are your 3 most popular contributions to the actions marketplace and to this list. https://seladb.github.io/StarTrack-js/#/preload?r=peaceiris,actions-hugo&r=peaceiris,actions-mdbook&r=peaceiris,actions-gh-pages

The actions went relatively unnoticed until they were added to the list and would not have met your criteria for acceptance. After that, people started noticing that some of your contributions were awesome actions.

To me this is indicative that people are more likely to find actions that fit their needs in this list than they are in the actions marketplace.

@gortcodes commented on GitHub (Mar 6, 2020): I'd recommend regular pruning over gating additions. Many of the actions in the list with a substantial number of stars did not start receiving stars until they were added to the list. @peaceiris as an example, here are your 3 most popular contributions to the actions marketplace and to this list. https://seladb.github.io/StarTrack-js/#/preload?r=peaceiris,actions-hugo&r=peaceiris,actions-mdbook&r=peaceiris,actions-gh-pages The actions went relatively unnoticed until they were added to the list and would not have met your criteria for acceptance. After that, people started noticing that some of your contributions were _awesome actions._ To me this is indicative that people are more likely to find actions that fit their needs in this list than they are in the actions marketplace.

GiteaMirror commented

2026-05-01 21:17:21 -05:00

@peaceiris commented on GitHub (Mar 6, 2020):

The actions went relatively unnoticed until they were added to the list and would not have met your criteria for acceptance. After that, people started noticing that some of your contributions were awesome actions.

Yes, It looks like a possible story.

A matter of main concern is maintainability. The more new actions, the more burden for reviewing by maintainers of this repository. I started to worry about this at #321. I do not want to repeat the heavy work. If the maintainers can have time to review, merge, and pruning all pull requests or links, I think we do not need our policy. Actually, it looks difficult in the future.

@jessicalostinspace suggests creating a check tool and @gortcodes mentioned regular pruning. I also think those approaches are good, but who does that?

By the way, I think my case is a very special case. (peaceiris/actions-gh-pages was featured by GitHub, I contributed some problems related to Actions since beta v1, I wrote some posts, and so on.) I do not know whether users notice my projects on this awesome list, or not. It is thought that the influence is small.

@peaceiris commented on GitHub (Mar 6, 2020): > The actions went relatively unnoticed until they were added to the list and would not have met your criteria for acceptance. After that, people started noticing that some of your contributions were awesome actions. Yes, It looks like a possible story. *A matter of main concern is maintainability*. The more new actions, the more burden for reviewing by maintainers of this repository. I started to worry about this at #321. I do not want to repeat the heavy work. If the maintainers can have time to review, merge, and pruning all pull requests or links, I think we do not need our policy. Actually, it looks difficult in the future. @jessicalostinspace suggests creating a check tool and @gortcodes mentioned regular pruning. I also think those approaches are good, but who does that? By the way, I think my case is a very special case. ([peaceiris/actions-gh-pages](https://github.com/peaceiris/actions-gh-pages) was featured by GitHub, I contributed some problems related to Actions since beta v1, I wrote some posts, and so on.) I do not know whether users notice my projects on this awesome list, or not. It is thought that the influence is small.

GiteaMirror commented

2026-05-01 21:17:22 -05:00

@sdras commented on GitHub (Mar 8, 2020):

Thanks for the concern, @peaceiris but I agree with @gortcodes' statement. I also don't want to gate people away from being able to contribute until their action is very well used, that's a surefire way to cut off an ecosystem and gatekeep. It's true that maintaining the repo takes time, which is why Gary and now Jessica are helping. I'd be up for periodic review with the two of them to prune out anything that isn't working well for the list.

@sdras commented on GitHub (Mar 8, 2020): Thanks for the concern, @peaceiris but I agree with @gortcodes' statement. I also don't want to gate people away from being able to contribute until their action is very well used, that's a surefire way to cut off an ecosystem and gatekeep. It's true that maintaining the repo takes time, which is why Gary and now Jessica are helping. I'd be up for periodic review with the two of them to prune out anything that isn't working well for the list.

GiteaMirror commented

2026-05-01 21:17:22 -05:00

@orozcoadrian commented on GitHub (Mar 8, 2020):

my 2-cents: I agree more with @peaceiris but I appreciate the compromise concluded by the repo owner. Since "how awesome" this list is now depends on the periodic curation/pruning by contributors, can we add a prominent display of "last reviewed on [date]"? That will hopefully also inform users that this specific list performs its curation "after-the-fact" as opposed to as a gate before inclusion.

By "how awesome this list is" what I mean is "how closely does this list meet the spirit of "awesome lists"

I'd be happy to help by creating a small PR to just update that date whenever I see that a pruning PR has been merged.

@orozcoadrian commented on GitHub (Mar 8, 2020): my 2-cents: I agree more with @peaceiris but I appreciate the compromise concluded by the repo owner. Since "how awesome" this list is now depends on the periodic curation/pruning by contributors, can we add a prominent display of "last reviewed on [date]"? That will hopefully also inform users that this specific list performs its curation "after-the-fact" as opposed to as a gate before inclusion. By "how awesome this list is" what I mean is "how closely does this list meet the spirit of ["awesome lists"](https://github.com/sindresorhus/awesome/blob/master/awesome.md#only-awesome-is-awesome) I'd be happy to help by creating a small PR to just update that date whenever I see that a pruning PR has been merged.

GiteaMirror commented

2026-05-01 21:17:24 -05:00

@peaceiris commented on GitHub (Mar 9, 2020):

I totally agree with @orozcoadrian :-)

@peaceiris commented on GitHub (Mar 9, 2020): I totally agree with @orozcoadrian :-)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-actions#4199