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

Update default for acceptable_conclusions #250

Merged
merged 2 commits into from
Jul 11, 2024

Conversation

CasperWA
Copy link
Owner

Closes #249

Updated to mirror standard GitHub behavior, where skipped is considered an acceptable conclusion to a workflow or job step.

Updated to mirror standard GitHub behaviour, where `skipped` is
considered an acceptable conclusion to a workflow or job step.
@CasperWA
Copy link
Owner Author

@MattiSG do you have any comments on these changes?

Copy link
Contributor

@MattiSG MattiSG left a comment

Choose a reason for hiding this comment

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

Thanks for pinging! 😊

README.md Outdated Show resolved Hide resolved
action.yml Outdated Show resolved Hide resolved
@MattiSG
Copy link
Contributor

MattiSG commented Jul 11, 2024

I don't know what's your release process, but I notice that this PR does not include a changelog nor a version number bump 🙂

@CasperWA
Copy link
Owner Author

I don't know what's your release process, but I notice that this PR does not include a changelog nor a version number bump 🙂

Indeed. PRs merge into main. Versioned releases are made separately based on the latest commit on main. Standard procedure. This means, as a rule of thumb, for GitHub Action repos, never point to a branch (unless explicitly stated one should do this in the repo's documentation).
I can release a new version after this has been merged.

Remove previously added examples as they are redundant.

Co-authored-by: Matti Schneider <gh@mattischneider.fr>
@CasperWA CasperWA enabled auto-merge (squash) July 11, 2024 11:59
@CasperWA CasperWA merged commit dd0f8c9 into main Jul 11, 2024
11 checks passed
@CasperWA CasperWA deleted the cwa/close-249-mirror-github-acceptable-conclusions branch July 11, 2024 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mirror GitHub interpretation in default acceptable conclusions
2 participants