Skip to content

Remove fish_variables from version control - #2

Draft
ignasxv with Copilot wants to merge 2 commits into
mainfrom
copilot/check-exposed-secrets
Draft

Remove fish_variables from version control#2
ignasxv with Copilot wants to merge 2 commits into
mainfrom
copilot/check-exposed-secrets

Conversation

Copilot AI commented Mar 5, 2026

Copy link
Copy Markdown

fish_variables is an auto-generated fish universal variable state file that was committed to the repo. While no active secrets were present, the file contained personal system paths and — critically — any set -Ux variable (API keys, tokens, etc.) would be serialized here and silently committed.

Changes

  • Removed fish/.config/fish/fish_variables from git tracking (git rm --cached)
  • Added .gitignore entry to permanently exclude the file
# Fish shell universal variables - machine-specific and may contain sensitive environment variables
fish/.config/fish/fish_variables
Original prompt

This section details on the original issue you should resolve

<issue_title>Exposed secreta</issue_title>
<issue_description>Is there any exposed secrets in this repo</issue_description>

<agent_instructions>Check if there’s any exposed secrets </agent_instructions>

Comments on the Issue (you are @copilot in this section)


🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Co-authored-by: ignasxv <62844231+ignasxv@users.noreply.github.com>
Copilot AI changed the title [WIP] Check for exposed secrets in repository Remove fish_variables from version control Mar 5, 2026
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.

Exposed secreta

2 participants