-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix integration test for merge in the main branch #63
fix integration test for merge in the main branch #63
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some documentation suggestions from my side.
If we want to merge in the main branch, we do it because we want to publish the package. Therefore, we need to be sure that there is an existing version of the dependent QED packages that works with the new version of the package we want to release. The integration tests are tested against the development branch and the release version. - The dev branch version must pass, as this means that the latest version of the other QED packages is compatible with our release version. - The release version can exist. If they exist, it means that we do not need to release a new version of this package.
bf77d43
to
da08934
Compare
The pipeline looks like expected: QEDjl-project/QEDcore.jl#57 |
Can you test it with a PR in QEDbase too? We should see the QEDprocesses Release test fail there. |
Yes I can. I was actual wondering, why it didn't failed. Now, I know I choose the wrong QED project 😅 |
The test run in QEDbase was successful and working as intended 👍 |
If we want to merge in the main branch, we do it because we want to publish the package. Therefore, we need to be sure that there is an existing version of the dependent QED packages that works with the new version of the package we want to release. The integration tests are tested against the development branch and the release version.
I will open an test PR to test if the feature is correctly working. If it is working, I mark the PR for ready for review.