Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

My workflow has been disabled even if I use this action #34

Closed
julienloizelet opened this issue May 14, 2024 · 2 comments
Closed

My workflow has been disabled even if I use this action #34

julienloizelet opened this issue May 14, 2024 · 2 comments

Comments

@julienloizelet
Copy link

Hi,

Am I doing something wrong or is this a bug ?

Every week, I run the v2 version of this action using a simple "Keep Alive" action: https://github.com/julienloizelet/ddev-tools/actions/workflows/keepalive.yml

I use it so that another "test" action is not disabled:

https://github.com/julienloizelet/ddev-tools/actions/workflows/tests.yml

But, it has been disabled today:


Screenshot 2024-05-14 at 16 36 32

I don't see any error in the Keep Alive workflow:


Screenshot 2024-05-14 at 16 39 28

But despite this, the "test" action has been deactivated.

Do you have an idea of what could be the reason of this behavior ?

Thanks !

@julienloizelet
Copy link
Author

julienloizelet commented May 14, 2024

I just found this release note: https://github.com/gautamkrishnar/keepalive-workflow/releases/tag/2.0.1
and I think I've found the cause of my problem.

As I started using this action with the dummy commit of v1, it was already working to have a separate "keep alive" workflow: all scheduled workflows were kept alive as a new commit was detected.

With the v2, if we use a separate "keep alive" workflow, we have to specify which workflow we want to keep active ?

Please let me know if I'm right. If it is correct, maybe it could useful to update this part of the README: https://github.com/gautamkrishnar/keepalive-workflow/?tab=readme-ov-file#migrating-from-v1-to-v2
(because a separate workflow file worked with the v1 and migrating to v2 involves managing a workflow_files input)

Thanks

@gautamkrishnar
Copy link
Owner

@julienloizelet yes you are right. With v2 you need to add it to every individual workflows you want to keep alive. Or you can also simply use workflow_files to manually specify multiple workflows.

Check the example https://github.com/gautamkrishnar/keepalive-workflow?tab=readme-ov-file#advanced-use-cases

name: Keepalive Workflow
on:
  schedule:
    - cron: "0 0 * * *"
permissions:
  actions: write
jobs:
  cronjob-based-github-action:
    name: Keepalive Workflow
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: gautamkrishnar/keepalive-workflow@v2
        with:
          workflow_files: "build1.yml, build2.yml"
          time_elapsed: "0"

Repository owner locked and limited conversation to collaborators May 16, 2024
@gautamkrishnar gautamkrishnar converted this issue into discussion #35 May 16, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants