-
Notifications
You must be signed in to change notification settings - Fork 3
Merge develop to master #215
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
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
c5ebe10
Add Google Maps API key to deployment workflow
CSE-Shaco e34cbe9
Merge pull request #211 from GDGoCINHA/master
CSE-Shaco 202f191
[ImgBot] Optimize images
ImgBotApp 97f16a2
fix(homecoming): typo 수정
CSE-Shaco 62979dd
Merge pull request #213 from CSE-Shaco/develop
CSE-Shaco f735af2
Merge pull request #212 from GDGoCINHA/imgbot
CSE-Shaco e985490
Include GOOGLE_MAPS_API_KEY in deploy workflow
CSE-Shaco eae9636
fix(homecoming): 디버깅을 위한 코드 추가
CSE-Shaco 9e08ff5
Merge pull request #214 from CSE-Shaco/develop
CSE-Shaco File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Check failure
Code scanning / CodeQL
Clear-text logging of sensitive information High
Copilot Autofix
AI 3 months ago
To address this logging of sensitive information, all code that logs (or otherwise exposes) any part of the
NEXT_PUBLIC_GOOGLE_MAPS_API_KEYvariable should be removed, especially the console statement on line 227. Simply remove theconsole.logblock (lines 225-228) from theHomecomingMapfunction insrc/app/homecoming/page.jsx. No imports, method replacements, or variable substitutions are required—just deleting the logging code is sufficient. This change will prevent the accidental or intentional logging of any part of the sensitive API key.