-
Notifications
You must be signed in to change notification settings - Fork 1
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
Disable code scanning default setup #3
Conversation
Signed-off-by: Sebastian Thomschke <[email protected]>
This is your friendly self-service bot. Thank you for raising a pull request to update the configuration of your GitHub organization. The following conditions need to fulfilled for auto-merging to be available:
Otterdog commands and optionsYou can trigger otterdog actions by commenting on this PR:
|
This is your friendly self-service bot. Diff for 3c35c5dOrganization technology.tm4e[id=eclipse-tm4e]
there have been 1 validation infos, enable verbose output with '-v' to to display them.
! repository[name="tm4e"] {
! code_scanning_default_setup_enabled = true -> false
! }
Plan: 0 to add, 1 to change, 0 to delete. |
This is your friendly self-service bot. The current configuration is out-of-sync with the live settings: Diff to live settingsOrganization technology.tm4e[id=eclipse-tm4e]
there have been 1 validation infos, enable verbose output with '-v' to to display them.
! repository[name="tm4e"] {
! code_scanning_default_languages = [
- javascript
- typescript
! ]
! }
Plan: 0 to add, 1 to change, 0 to delete. The current configuration needs to be updated to reflect the live settings otherwise they would be overwritten when this PR gets merged. cc @eclipse-tm4e/eclipsefdn-security cc @eclipse-tm4e/eclipsefdn-releng |
@netomi as far as I understand I need to disable the code scanning default setup for my PR with a custom codeql workflow to succeed. eclipse-tm4e/tm4e#826 |
I disabled codeql default setup manually and update the config already. Something has changed from GitHub side as this is not working at all anymore. Sorry for the inconvenience, going to take a look at the configuration, but with the custom workflow it should work reliable afaict. |
This is required to run custom codeql workflows