-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
do not run the scheduled GitHub actions or CIFuzz on forks / some small cleanups #6107
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.
lgtm
@chipitsine your change inspired me - this makes sense, right? |
yes, it makes sense. I;m not sure why release workflow should be limited to parent repo only, but ok |
Because currently it is only build for the release/tag branches which should only be used by the parent. There are plans to rework this as part of https://trac.cppcheck.net/ticket/10771. |
Yes, this is fine as well.
…On Mon, Mar 11, 2024, 13:52 Oliver Stöneberg ***@***.***> wrote:
I;m not sure why release workflow should be limited to parent repo only,
but ok
Because currently it is only build for the release/tag branches which
should only be used by the parent. There are plans to rework this as part
of https://trac.cppcheck.net/ticket/10771.
—
Reply to this email directly, view it on GitHub
<#6107 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ5KUGA2VDZH2WGSY6CMJDYXV5HRAVCNFSM6AAAAABEOGXKYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBYGAYTENJYGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks a lot for the feedback! |
No description provided.