Skip to content

fix: use getBooleanInput instead of getInput #92

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

Jump to bottom
Merged
styfle merged 2 commits into from
May 28, 2021
Merged

fix: use getBooleanInput instead of getInput #92

styfle merged 2 commits into from
May 28, 2021

Conversation

@Warashi
Copy link
Contributor

@Warashi Warashi commented May 27, 2021

FIX: #91

@Warashi
Copy link
Contributor Author

Warashi commented May 27, 2021

oops, action is failed at my forked repository.
I'm trying to fix now.

@Warashi Warashi force-pushed the feature/use-getbooleaninput branch from 237edb3 to 17a7861 Compare May 27, 2021 23:09
@Warashi
Copy link
Contributor Author

Warashi commented May 27, 2021

Fixed.
Workflow_id of long.yml and longer.yml may different at my fork repository, so main.yml did not cancel them.
After approval of running workflows, I will push twice to test cancel.

styfle
styfle approved these changes May 28, 2021
View reviewed changes
Copy link
Owner

@styfle styfle left a comment

Choose a reason for hiding this comment

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

Thanks!

@styfle styfle merged commit f905655 into styfle:main May 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@styfle styfle styfle approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Use getBooleanInput to get ignore_sha and all_but_latest

2 participants

@Warashi @styfle