Skip to content

Conversation

ali90h
Copy link
Contributor

@ali90h ali90h commented Aug 13, 2025

Add comprehensive troubleshooting section to DEVELOPMENT.md

Description

Addresses issue #5025 by adding a dedicated Troubleshooting section to the developer documentation. This section provides solutions for common development environment issues that can cause significant developer friction.

Changes Made

Problem Solved

Developers encountering common setup issues (like the case-sensitive filesystem problem with Turbo) previously had to hunt through various toolchain documentation and GitHub issues. This change provides centralized, easily discoverable solutions that should reduce developer onboarding friction and debugging time.

Testing

  • Verified all markdown links are functional
  • Confirmed formatting matches existing documentation style
  • Verified Table of Contents anchor links work correctly

Related Issues

Closes #5025

Checklist

  • My changes follow the project's coding standards
  • I have tested the documentation changes
  • All links and references have been verified

ali90h added 2 commits August 13, 2025 02:51
- Add comprehensive troubleshooting section between Debugging and Building
- Include solutions for case-sensitive volume issues with Turbo
- Add Turbo daemon fixes and cache clearing procedures
- Cover platform-specific issues and Node.js/pnpm problems
- Provide links to toolchain-specific GitHub issues
- Update Table of Contents with new section

Addresses gitbutlerapp#5025
- Add comprehensive troubleshooting section between Debugging and Building
- Include solutions for case-sensitive volume issues with Turbo
- Add Turbo daemon fixes and cache clearing procedures
- Cover platform-specific issues and Node.js/pnpm problems
- Provide links to toolchain-specific GitHub issues
- Update Table of Contents with new section

Addresses gitbutlerapp#5025
Copy link

vercel bot commented Aug 13, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Project Deployment Preview Comments Updated (UTC)
gitbutler-components Ready Preview Comment Aug 13, 2025 10:38am

Copy link

vercel bot commented Aug 13, 2025

@ali90h is attempting to deploy a commit to the GitButler Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Collaborator

@Byron Byron left a comment

Choose a reason for hiding this comment

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

Thanks a lot for improving the documentation, it's much appreciated!

Did you run into any of these issues yourself? Ideally we only add common real-world pain-points and keep solutions specific.

DEVELOPMENT.md Outdated
$ pnpm dev:desktop
```

### Cache Issues
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could you lower-case issues in all the headings?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done — normalized “issues” to lower-case across all headings.

DEVELOPMENT.md Outdated
Comment on lines 278 to 281
#### Linux

- Double-check all system dependencies are installed (see Prerequisites)
- On some distributions, you may need additional development packages
Copy link
Collaborator

Choose a reason for hiding this comment

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

I find this too vague to the point where it can be removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed the generic Linux

DEVELOPMENT.md Outdated
Comment on lines 308 to 317
#### Cargo build failures

```bash
# Update Rust toolchain
$ rustup update

# Clean and rebuild
$ cargo clean
$ cargo build
```
Copy link
Collaborator

Choose a reason for hiding this comment

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

rust-toolchain.toml assures the correct Rust compiler is used. So I think this is too general and is either removed or replaced by something more specific.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed the generic Rust section.

DEVELOPMENT.md Outdated
Comment on lines 319 to 321
#### Missing system dependencies

On Linux, if you're getting linking errors, ensure all required system libraries are installed. Revisit the Prerequisites section for your distribution.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Again, I think this is too general and should be removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

Co-authored-by: Sebastian Thiel <[email protected]>
@ali90h
Copy link
Contributor Author

ali90h commented Aug 13, 2025

Thanks for the review! I’ve addressed all comments:

  • demoted heading level
  • lower-cased “issues”
  • removed generic Linux/Rust sections
  • kept only concrete, reproducible items

Ready for another pass. 🙏

Copy link
Collaborator

@Byron Byron left a comment

Choose a reason for hiding this comment

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

Awesome, it looks great to me!

As it's a little bit outside of my area of expertise, let's be sure this works for @krlvi as well.

@krlvi
Copy link
Member

krlvi commented Aug 14, 2025

Hi @ali90h, thank you so much for taking from your time to improve the documentation, it is really appreciated! 🙇‍♂️

@krlvi krlvi merged commit 35152af into gitbutlerapp:master Aug 14, 2025
20 of 21 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.

Inclusion of troubleshooting information on developer docs
3 participants