Your branch need to be up to date with origin/main
Update your git repository git fetch origin if origin is this remote
Check format style with the script provided in scripts/source-format-all.sh
You must use clang-format style (github CI version is 11)
Your proposal must include a commit where the file CHANGELOG is updated (add a line describing the proposed change + PR id, see file for examples). If your contribution is significant, you can also ask to be added to the contributor list in the discussion.
These checks are enforced by github workflow actionsPlease refer to the corresponding log in case of failure
UPDATE the form below to describe your PR
Please check if the PR fulfills these requirements
[x] The commit message follows our guidelines (see CONTRIBUTING)
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
Be aware that the PR request cannot be accepted if it doesn't pass the Continuous Integration tests.
What kind of change does this PR introduce?
[ ] bug fix
[ ] feature
[ ] docs update
[x] other: CI feature
What is the current behavior? (You can also link to an open issue here)
Tests regression are not cached.
What is the new behavior (if this is a feature change)?
Caching regression tests to avoid software decline in performance.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
hiergaut
commented
4 months ago
Pull Request Desription
Check if you branch history is PR compatible
git fetch originif origin is this remotescripts/source-format-all.shUPDATE the form below to describe your PR
Please check if the PR fulfills these requirements
Be aware that the PR request cannot be accepted if it doesn't pass the Continuous Integration tests.
What kind of change does this PR introduce?
What is the current behavior? (You can also link to an open issue here) Tests regression are not cached.
What is the new behavior (if this is a feature change)? Caching regression tests to avoid software decline in performance.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: