secureli icon indicating copy to clipboard operation
secureli copied to clipboard

Fix secureli-release-noop step in pipeline

Open tdurk93 opened this issue 2 years ago • 0 comments

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.

tdurk93 avatar Jan 19 '24 22:01 tdurk93