-
Notifications
You must be signed in to change notification settings - Fork 2
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
Github action for publishing broken #21
Comments
woop!! super good eye tysm!! i enabled the workflow and forced the action, @tyleretters / @tehn / @p3r7 does that seem like all that’s needed? |
seems like so... thanks for reporting. i wonder if this auto-disabling could not be be... disabled. |
interesting. yeah sounds like a cost-management thing to prevent legions of zombie actions from running.... not sure what a fix is other than making sure "activity" happens on this repo every 59 days. |
I think the fix might be to remove the scheduled trigger. Running the action on push should be sufficient to keep the site updated, right? |
@Dewb yes and we'd need "on push" from https://github.com/monome/norns-community as well. something like this: https://stackoverflow.com/questions/74775432/trigger-another-repo-in-github-actions |
Just popping in to bump this issue. Seems like the workflow was disabled again and no new scripts have been added to the page since early January. |
thanks for the bump @tapecanvas. @dndrks just ran the action so everything should be showing up now |
@dndrks @tehn what do you all think of adding an on push trigger as mentioned in #21 (comment) ? |
sounds good to me!
…On Fri, Mar 8, 2024, 3:41 PM Tyler Etters ***@***.***> wrote:
@dndrks <https://github.com/dndrks> @tehn <https://github.com/tehn> what
do you all think of adding an on push trigger as mentioned in #21
(comment)
<#21 (comment)>
?
—
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB4I4H27YCT4JG5YFHNJMTYXIPAXAVCNFSM6AAAAAA7DI42EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWGM4DQMJSHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I think the scheduled activity for publishing community changes is broken. The github action says:
"This scheduled workflow is disabled because there hasn't been activity in this repository for at least 60 days. Enable this workflow to resume scheduled runs. "
The text was updated successfully, but these errors were encountered: