Skip to content

Added information on continuing to run workflows #16717

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.

Sign up for GitHub

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

Closed
HammyHavoc wants to merge 1 commit into from
Closed

Added information on continuing to run workflows #16717

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion data/reusables/actions/scheduled-workflows-disabled.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
To prevent unnecessary workflow runs, scheduled workflows may be disabled automatically. When a public repository is forked, scheduled workflows are disabled by default. In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days.
To prevent unnecessary workflow runs, scheduled workflows may be disabled automatically. When a public repository is forked, scheduled workflows are disabled by default. In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days. You can continue to run scheduled workflows without repository activity by visiting the workflow's page and clicking `Continue running workflow`.

@ethomson ethomson Apr 6, 2022

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm generally +1 on documenting this, it seems useful. I'm not sure that it should be in the reusable, though, it seems like it should only be a part of the disabling-and-enabling-a-workflow page. It would fit in nicely there and breaking it out of the reusable allows us to expand the instructions so that it's a little more verbose and step-by-step than just "[visit] the workflow's page".

I wonder if the docs team has any thoughts here...

@skedwards88 skedwards88 Apr 6, 2022

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with @ethomson . This reusable is also used in the "Usage limits, billing, and administration" article, but the added info is really only relevant to the "Disabling and enabling a workflow" article. Adding this info to the "Disabling and enabling a workflow" article (content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md) instead makes sense.

(To help orient you in that file: this reusable is referred to as{% data reusables.actions.scheduled-workflows-disabled %}. You can find more info about reusables here.)

I also agree that we could give users a bit more context. Since this is almost identical to enabling a workflow, maybe we can can say something like:

To continue to run a scheduled workflow that was disabled due to no repository activity, follow the steps under [Enabling a workflow](#enabling-a-workflow) and click `Continue running workflow`.

Alternatively, we could add a new section that is similar to the Enabling a workflow section