Skip to content

fix(amazonq): enable local context for falcon #7176

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

Merged
merged 1 commit into from
Apr 26, 2025

Conversation

zixlin7
Copy link
Contributor

@zixlin7 zixlin7 commented Apr 26, 2025

Problem

context items should be always on and not controlled by workspace setting
there need to be a separate setting to control @workspace indexing, out of scope for this PR

Solution


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@zixlin7 zixlin7 requested a review from a team as a code owner April 26, 2025 01:56
Copy link

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.
  • This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
    • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
    • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

@zixlin7 zixlin7 changed the title fix: enable local context for falcon fix(amazonq): enable local context for falcon Apr 26, 2025
@zixlin7
Copy link
Contributor Author

zixlin7 commented Apr 26, 2025

/retryBuilds

@jpinkney-aws jpinkney-aws merged commit 3beb8b2 into aws:feature/hybridChat Apr 26, 2025
19 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants