Revert "Fix masking logic for file output"

[maidul98]

Reverts #12

Summary by CodeRabbit

• Refactor
  • Improved the handling of secret values by masking each secret immediately before it is exported as an environment variable, rather than masking all secrets upfront.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The update modifies the process of masking secret values in GitHub logs. Previously, all secrets were masked immediately after fetching. With this change, secrets are now masked individually right before each is exported as an environment variable, within the relevant conditional block. No other logic or error handling was altered in this revision.

Changes

File(s)	Change Summary
index.js	Moved the masking of secrets from a loop after fetching to within the conditional block that exports secrets as environment variables. Each secret is now masked immediately before export.

Sequence Diagram(s)

sequenceDiagram
    participant Fetcher as Secrets Fetcher
    participant Exporter as Env Exporter
    participant Logger as GitHub Logs

    Fetcher->>Fetcher: Fetch all secrets
    loop For each secret
        alt If exporting as env variable
            Exporter->>Logger: Mask secret value
            Exporter->>Exporter: Export as env variable
        end
    end

Loading

Possibly related PRs

• Fix masking logic for file output #12: Adjusts the timing and placement of secret masking in relation to exporting secrets as environment variables, directly affecting how and when core.setSecret is used.

Poem

A secret kept, a whisper masked,
Now hidden just before the task.
No longer all at once, but neat—
Each secret masked before it greets
The world as env, so logs stay clean,
A rabbit’s hop in code unseen!
🐇✨

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 66df24e and 06d25f4.

📒 Files selected for processing (1)

• index.js (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.