fix(claude-code): source bashrc file only if it exists

[schahal]

Closes #458

Description

It only sources the bashrc file if it exists (as the startup/install scripts will fail if the workspace doesn't have that)

Type of Change

• New module
• Bug fix
• Feature/enhancement
• Documentation
• Other

Module Information

Path: registry/coder/modules/claude-code
New version: v3.0.2 <--- Maintainers, I'll have to lookup how to bump this for this project
Breaking change: [ ] Yes [x] No

Testing & Validation

• Tests pass (bun test)
• Code formatted (bun run fmt)
• Changes tested locally

Related Issues

[schahal]

@DevelopmentCats , I'm trying to follow CONTRIBUTING.md, but running

./.github/scripts/version-bump.sh patch

on this branch doesn't return anything:

$ ./.github/scripts/version-bump.sh patch
🔍 Detecting modified modules...
$

Are there other steps needed, you think?

[DevelopmentCats]

@DevelopmentCats , I'm trying to follow CONTRIBUTING.md, but running

./.github/scripts/version-bump.sh patch

on this branch doesn't return anything:

$ ./.github/scripts/version-bump.sh patch
🔍 Detecting modified modules...
$

Are there other steps needed, you think?

You can just manually replace the versions in README if you want.

This script essentially just updates all the version references in the README to match what they should based on the last tag and requested bump type.

Does the script not exist for you at all in your version?

[schahal]

Thanks, I bumped the version!

_{(i think the "issue" with the script was this line in the script: changed_files=$(git diff --name-only "${base_ref}"...HEAD), which may not detect in my situation as my pr branch is main of my fork (which base_ref defaults to, so equals HEAD... i think)}

[matifali]

Thanks for your contribution

[schahal]

👍 thank you for the quick iterations!

Looks like the PR didn't auto-merge because the branch was out-of-date, so I just updated.