You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a SeCurLI user, I want SeCurLI to simulate the behavior as if it were running in the main branch.
So that we can correct our semantic-release dry-run step HERE to serve as a valid test.
Currently, because SeCurLI is ran on PR branches, it always exits with the following message:
branch '' isn't in any
release groups; no release will be made
We need to figure out how to make SeCurLI simulate the behavior as if it were running in the main branch which could require fixing the release group to include all branches.
AC:
- SeCurLI simulates the behavior of running on the main branch
- Semantic-release dry-run is served as a valid test
Open Questions:
- Why does this step use the github action relekang/python-semantic-release instead of python-semantic-release/python-semantic-release, which is what we use in the actual release? We may need to swap that test is using the same Action as the actual release.
The text was updated successfully, but these errors were encountered:
As a SeCurLI user, I want SeCurLI to simulate the behavior as if it were running in the main branch.
So that we can correct our semantic-release dry-run step HERE to serve as a valid test.
Currently, because SeCurLI is ran on PR branches, it always exits with the following message:
branch '' isn't in any
release groups; no release will be made
We need to figure out how to make SeCurLI simulate the behavior as if it were running in the main branch which could require fixing the release group to include all branches.
AC:
- SeCurLI simulates the behavior of running on the main branch
- Semantic-release dry-run is served as a valid test
Open Questions:
- Why does this step use the github action relekang/python-semantic-release instead of python-semantic-release/python-semantic-release, which is what we use in the actual release? We may need to swap that test is using the same Action as the actual release.
The text was updated successfully, but these errors were encountered: