Why didn't the CI workflow run when I pushed to my feature branch?

Why this happens

The page describes the snippet as a way to trigger a scan of a profile on merge, and it lists main as the only branch. So a push elsewhere starts nothing. That is how the file was written, and not a fault in Cyberlop.

How to fix it

1. Open cyberlop-scan.yml from the first tab of Integrations in your repository.
2. The snippet says on: push to branches [main], plus workflow_dispatch.
3. Add the feature branch name to the branches list, or use a pattern that suits your team.
4. Use the manual run option in your code host’s workflow page and choose the branch.
5. Confirm CYBERLOP_URL and CYBERLOP_API_TOKEN exist as repository secrets.

The job is also non-blocking. It prints findings to the build log and never fails the build. So when it does run, a green build does not mean there were no findings.

Still not working?

The target’s Repo branch decides which code the scan reads, not the branch that fired the job. A target set to main reads main. See why a scan tested main. The second tab’s snippet is for the other supported code host, and its capture did not list branch rules, so read the file you copied. More: when the CI workflow runs and why CI passes with findings. You can also use the contact page.

Related questions

• When does the generated CI workflow run?
• How do I trigger a Cyberlop scan from my CI pipeline?
• How do I copy the ready-made CI workflow for my code host?
• How do I scan a branch other than main?
• Can I scan a specific commit instead of the latest one?

Full tutorial

How to add security scanning to your CI/CD pipeline

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre