Skip to content
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

add option to keep debug symbols for build #84

Merged
merged 2 commits into from
Mar 12, 2025
Merged

Conversation

js-9
Copy link
Contributor

@js-9 js-9 commented Mar 12, 2025

Changes

  • adds an input to allow to keep pdb files to be able to publish debug builds to steam

Checklist

  • Read the contribution guide and accept the code of conduct
  • Readme (updated or not needed)
  • Tests (added, updated or not needed)

Summary by CodeRabbit

  • New Features
    • Introduced a new configuration option "debugBranch" that enables the upload of debug files if set to true.
    • Updated deployment documentation and configuration parameters to clarify when debug files are included.
    • Added conditional logic to dynamically adjust file exclusions during the deployment process.

Copy link

coderabbitai bot commented Mar 12, 2025

Walkthrough

The changes add a new configuration option, debugBranch, to the Steam Deploy GitHub Action. This option is documented in the README and implemented in both action.yml and steam_deploy.sh. When enabled, it allows the inclusion of debug files by altering file exclusion logic during the deployment process. The new parameter defaults to false, maintaining previous behavior unless explicitly overridden.

Changes

Files Change Summary
README.md & action.yml Added new configuration option/parameter debugBranch (default: false) to allow conditional inclusion of debug files and symbols in uploads.
steam_deploy.sh Introduced conditional logic that sets the debugExcludes variable based on the debugBranch value, dynamically modifying the depot manifest.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant Runner as GitHub Action Runner
    participant Script as steam_deploy.sh

    Dev->>Runner: Set debugBranch parameter (true/false)
    Runner->>Script: Pass environment variable debugBranch
    Script->>Script: Evaluate debugBranch value
    alt Debug enabled
        Script->>Script: Set debugExcludes to ""
    else Debug disabled
        Script->>Script: Set debugExcludes with exclusion patterns
    end
    Script->>Runner: Generate depot manifest with appropriate exclusions
Loading

Suggested reviewers

  • davidmfinol

Poem

I'm a jolly rabbit, hopping with glee,
Debug options now shine, as clear as can be!
A switch to guide our upload path so true,
Carrot dreams in code, refreshing like dew.
With every change, our scripts bloom anew!
🥕✨

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)
  • We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
    - To enable this feature, set early_access to true under in the settings.
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🔭 Outside diff range comments (1)
steam_deploy.sh (1)

1-7: 🛠️ Refactor suggestion

Initialize debugBranch to Prevent Unbound Variable Errors

Since the script is running with set -euo pipefail, referencing an unset variable like debugBranch can cause a runtime error. Although the action.yml sets a default, it is safer to initialize this variable explicitly in the script. Consider adding an initialization near the top of the file.

Proposed diff (insert after line 3):

 IFS=$'\n\t'
+debugBranch=${debugBranch:-false}
🧰 Tools
🪛 Shellcheck (0.10.0)

[warning] 7-7: rootPath is referenced but not assigned.

(SC2154)

🧹 Nitpick comments (3)
README.md (2)

185-187: Documentation Clarity for debugBranch Parameter

The new section for debugBranch clearly explains that when set to true, debug files will not be excluded from the upload. This documentation is concise and aligns well with the PR objective of enabling debug symbol retention.


191-191: Adjust Heading Level for Consistency

The heading “#### Excluded Files / Folders” immediately following a “## Other Notes” section violates the one-level increment guideline. Consider changing it to “### Excluded Files / Folders” for better readability and to satisfy markdownlint recommendations.

Proposed diff:

-#### Excluded Files / Folders
+### Excluded Files / Folders
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

191-191: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)

steam_deploy.sh (1)

44-48: Conditional Setting of Debug Exclusions

The new conditional block that determines the value of debugExcludes based on debugBranch is implemented correctly. When debugBranch is true, debug exclusions are disabled (empty string); otherwise, the file exclusion directives are applied.

🧰 Tools
🪛 Shellcheck (0.10.0)

[warning] 44-44: debugBranch is referenced but not assigned.

(SC2154)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 99e7436 and b075aa9.

📒 Files selected for processing (3)
  • README.md (1 hunks)
  • action.yml (2 hunks)
  • steam_deploy.sh (2 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md

191-191: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4

(MD001, heading-increment)

🪛 Shellcheck (0.10.0)
steam_deploy.sh

[warning] 44-44: debugBranch is referenced but not assigned.

(SC2154)

🔇 Additional comments (1)
action.yml (1)

85-89: New Input Parameter debugBranch Configuration

The new input parameter debugBranch is integrated correctly. It is declared as not required with a default of false and includes an appropriate description. The configuration is consistent with the intended use in both the documentation and the deployment script.

Copy link
Member

@davidmfinol davidmfinol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good suggestion!

@davidmfinol davidmfinol merged commit 7a0e17f into game-ci:main Mar 12, 2025
3 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.

2 participants