-
Notifications
You must be signed in to change notification settings - Fork 69
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
omit DWARF debug info when building BRO binaries #625
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Alexandre Lamarre <alexandre.lamarre@suse.com>
Will want to have this target |
/backport release/v6.0 |
Hmm. Odd - looks like the backport action failed because it doesn't identify you as a member of rancher org. 🤔 Seems odd, maybe an Okta profile issue? AFAIK if our SUSE okta has our GitHub username in the profile it will auto add/invite us to Rancher org. Also BTW @jbiers and I opted to start using |
/backport release/v6.x |
@alexandreLamarre - seems the backport command should work as intended now. At least barring permission issues:
As mentioned you may just need to adjust Okta settings to ensure your user shows up as in the Rancher org - if you are in the org, I think your membership needs to be public for it work. So that could be a factor too if you're in the org currently. If possible maybe we can create a workaround for that to allow that membership to stay private and still be identifiable. |
No description provided.