Skip to content
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

[BUG] GitHub action set for on:release not getting triggered #1351

Closed
samhita-alla opened this issue Aug 18, 2021 · 9 comments
Closed

[BUG] GitHub action set for on:release not getting triggered #1351

samhita-alla opened this issue Aug 18, 2021 · 9 comments
Labels
bug Something isn't working flytekit FlyteKit Python related issue good first issue Good for newcomers hacktoberfest untriaged This issues has not yet been looked at by the Maintainers

Comments

@samhita-alla
Copy link
Contributor

samhita-alla commented Aug 18, 2021

Describe the bug
A GitHub action set for on:release is not getting triggered when the release is first a draft and later published. Find the relevant GitHub action config here: https://github.com/flyteorg/flytekit/blob/master/.github/workflows/pythonpublish.yml

Expected behavior
GitHub action has to get triggered.

To Reproduce
Steps to reproduce the behavior:

  1. Create a draft release in the flytekit repo
  2. Publish the release
  3. All GitHub actions wouldn't trigger. Check https://github.com/flyteorg/flytekit/actions

GitHub repo(s)
flytekit

@samhita-alla samhita-alla added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers labels Aug 18, 2021
@yindia yindia added the good first issue Good for newcomers label Aug 28, 2021
@samhita-alla samhita-alla changed the title [BUG] Workflow set for on:release not triggering [BUG] GitHub action set for on:release not getting triggered Sep 23, 2021
@samhita-alla samhita-alla added flytekit FlyteKit Python related issue hacktoberfest labels Sep 23, 2021
@yindia yindia removed their assignment Oct 1, 2021
@sshiv5768
Copy link

Hey, @samhita-alla, I would love to work on this issue.

@samhita-alla
Copy link
Contributor Author

Hey, @samhita-alla, I would love to work on this issue.

Awesome! Please do. :)

@lordnodd
Copy link

lordnodd commented Oct 2, 2021

Hey @samhita-alla, I am not sure if github workflows have trigger for release created by draft. Here the official docs for event trigger through github actions mention that in a note github-actions-event-trigger.
edit: or am I not understanding this correctly?

@samhita-alla
Copy link
Contributor Author

Hey @samhita-alla, I am not sure if github workflows have trigger for release created by draft. Here the official docs for event trigger through github actions mention that in a note github-actions-event-trigger. edit: or am I not understanding this correctly?

@evalsocket Do we have a mechanism to fix this issue? As @lordnodd mentioned, GitHub docs clearly say that The release event is not triggered for draft releases..

@yindia
Copy link
Contributor

yindia commented Oct 10, 2021

@lordnodd Yes you are right. Use published trigger in place of created.

Note: The prereleased type will not trigger for pre-releases published from draft releases, but the published type will trigger. If you want a workflow to run when stable and pre-releases publish, subscribe to published instead of released and prereleased.

@samhita-alla
Copy link
Contributor Author

@lordnodd Yes you are right. Use published trigger in place of created.

Note: The prereleased type will not trigger for pre-releases published from draft releases, but the published type will trigger. If you want a workflow to run when stable and pre-releases publish, subscribe to published instead of released and prereleased.

@lordnodd, would you mind working on this?

@lordnodd
Copy link

Cool I'll give this a shot.

@lordnodd
Copy link

I made sure to read through the contribution docs, and updated the changes stated by @evalsocket, this is my first open-source commit, let me know if I missed out anywhere :)

@samhita-alla
Copy link
Contributor Author

I made sure to read through the contribution docs, and updated the changes stated by @evalsocket, this is my first open-source commit, let me know if I missed out anywhere :)

Thank you! Looks like your PR got merged. :)

@yindia yindia closed this as completed Oct 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working flytekit FlyteKit Python related issue good first issue Good for newcomers hacktoberfest untriaged This issues has not yet been looked at by the Maintainers
Projects
None yet
Development

No branches or pull requests

4 participants