-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pause on accepting on new community starter workflows #631
Comments
This comment has been minimized.
This comment has been minimized.
Good idea, pinned 🙇🏾 |
https://instagram.com/brunadiano68?igshid=1gcclzx7k1zea @ |
name: Super-Linter Run this workflow every time a new commit pushed to your repositoryon: push jobs: Set the job key. The key is displayed as the job namewhen a job name is not providedsuper-lint:
|
gh pr checkout 1212 |
Hi. I am really sorry about my repository there. And I would like to thank you for your contribution on saying so. Also, that was a long time ago, before the API and all the sources for the keys were working well. I deeply apologize for that. I was away for so long also and that is why I took long to come back in and see all the tasks I have :) Thank you again brother. |
This issue has become stale and will be closed automatically within a period of time. Sorry about that. |
Not stale. |
Hi all, Can someone please look into the required approvals needed to merge : #1512. It has been quite many days this is pending. |
Can we still suggest new future starter workflows through issues? Or is that also on hold right now? |
😼 |
This issue has become stale and will be closed automatically within a period of time. Sorry about that. |
Not stale. |
Hey! 👋 I know you're not accepting community workflows right now butI wanted to ask if you are interested in adding a starter workflow for the eleventy static site generator. If so I can submit a PR. Diff is here main...studioromeo:starter-workflows:pages/eleventy Workflow test repo: https://github.com/studioromeo/eleventy-action Thanks! |
This issue has become stale and will be closed automatically within a period of time. Sorry about that. |
👋🏾 Hi there
As you can probably tell, we haven't been very good at merging in new starter workflows in to this repository. First off I'd like to apologise to everyone who has submitted a new starter workflow. Thank you for submitting them and our apologies for not accepting them sooner.
We'd love to have more starter workflows appear on the Actions tab, but at this time the page just doesn't work well with lots of new starter workflows. Having a team try to process and understand the starter workflows hasn't worked too well.
Perhaps we need to make starter workflows more like the Marketplace, so a community can publish and update workflows without needing approval. That's something we are exploring for the future.
At this time I think its unfair to starter workflow authors to submit them and then have nothing happen with them for a long period of time. Rather than create unfair expectations we are temporarily going to stop accepting new starter workflows. We will try to merge all the ones already submitted, see below 👇🏾 for that list.
Sorry about that, but hope this is temporary and we'll figure something else out that's better for the future.
This are the starter workflows we are going to try and merge in:
The text was updated successfully, but these errors were encountered: