Cannot select existing CodeQL configuration when switching to Advanced setup

[OriginalMHV]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

Workflow Configuration

Discussion Details

Description:
When attempting to switch CodeQL analysis to "Advanced" mode, I'm prompted to create a new configuration file. However, I already have an existing CodeQL configuration in my repository. If I try to go back, the "Advanced" is not turned on.

Expected Behavior:
When selecting "Advanced" CodeQL analysis, I should be able to choose/use my existing configuration file
OR the system should detect the existing configuration and allow me to proceed

Actual Behavior:

• I'm forced to create a new configuration through the UI
• When I try to commit/push the new configuration, it fails because the file already exists
• This creates a deadlock where I cannot:
  • Use Advanced mode (because I can't complete the setup wizard)
  • Continue with my existing CodeQL setup in Advanced mode

Additional Context:
I need to configure JFrog integration, which requires Advanced mode. Both changes need to be implemented together, but the current workflow prevents me from proceeding.

Suggestion is to allow us to "Use existing configuration" when switching to Advanced mode

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Dave-Bronson-Greystone]

I found a solution, which isn't very obvious. But it works (for now).

Disable the Default setup:

• If "Default setup" is currently active, click the adjacent settings (three dots) menu and select Switch to advanced.
• In the pop-up window, click Disable CodeQL to turn off the default settings.

From the main Actions tab for your repo:

• Manually run the CodeQL option in the left pane that corresponds to the codeql.yml you already have in /workflows

Now the Code Scanning section in the repo's settings will be switched to Advanced, and using your existing workflow