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

ci: upgrade github actions #138

Merged
merged 1 commit into from
Oct 3, 2024
Merged

ci: upgrade github actions #138

merged 1 commit into from
Oct 3, 2024

Conversation

lampajr
Copy link
Member

@lampajr lampajr commented Oct 3, 2024

Thank you for submitting this pull request

Description

Upgrade the github action used in this CI to avoid:
image

How Has This Been Tested?

Checklist

  • Tests added if applicable.
  • Documentation updated if applicable.

Merge criteria:

  • The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

Note: dist/cli/index.js and dist/gha/index.js are automatically generated by git hooks and gh workflows.

First time here?

This project follows git conventional commits pattern, therefore the commits should have the following format:

<type>(<optional scope>): <subject>
empty separator line
<optional body>
empty separator line
<optional footer>

Where the type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test]

NOTE: if you are still in a work in progress branch and you want to push your changes remotely, consider adding --no-verify for both commit and push, e.g., git push origin <feat-branch> --no-verify - this could become useful to push changes where there are still tests failures. Once the pull request is ready, please amend the commit and force-push it to keep following the adopted git commit standard.

How to prepare for a new release?

There is no need to manually update package.json version and CHANGELOG.md information. This process has been automated in Prepare Release Github workflow.

Therefore whenever enough changes are merged into the main branch, one of the maintainers will trigger this workflow that will automatically update version and changelog based on the commits on the git tree.

More details can be found in package release section of the README.

Signed-off-by: Andrea Lamparelli <[email protected]>
Copy link
Contributor

github-actions bot commented Oct 3, 2024

Coverage report

St.
Category Percentage Covered / Total
🟢 Statements 89.71% 497/554
🟢 Branches 86.1% 192/223
🟢 Functions 87.4% 111/127
🟢 Lines 89.57% 481/537

Test suite run success

215 tests passing in 18 suites.

Report generated by 🧪jest coverage report action from 7f19fac

@lampajr lampajr merged commit 6d6592f into kiegroup:main Oct 3, 2024
6 checks passed
@lampajr lampajr deleted the update_gha branch October 3, 2024 18:04
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.

1 participant